Sponsored Content
Full Discussion: sar + sdXY,Z + /dev/dsk
Top Forums UNIX for Dummies Questions & Answers sar + sdXY,Z + /dev/dsk Post 40060 by Colf on Monday 8th of September 2003 08:36:38 AM
Old 09-08-2003
Really thanks.
It's helped.
 

10 More Discussions You Might Find Interesting

1. Solaris

mount: /dev/dsk/c0t6d0s0 no such device

I've searched through unix.com and google for this issue I am having on one particular Sun E280R with installing netbackup software from CD. I know the cd is good because i installed the software on 4 other servers right before this one. This is the issue I am seeing. vold does not mount the CD... (2 Replies)
Discussion started by: dangral
2 Replies

2. Solaris

pls help - /dev/dsk 100% full

I use the following command dk -k and get the following output: Filesystem kbytes used avail capacity Mounted on /dev/dsk/c0t0d0s0 1587078 56546 1482920 4% / /dev/dsk/c0t0d0s6 1984230 926199 998505 49% /usr /proc 0 0 0 ... (1 Reply)
Discussion started by: indianboy08
1 Replies

3. Solaris

anyone can tell me what is /dev/dsk/c3t600A0B80002FA5F50000000000000000d0s0?

Hi all, I just find some strange device (at least to me) on my Sun Blade server, CP3060, like below: bash-3.00# cd /dev/dsk bash-3.00# ls c3* c3t600A0B80002FA5F50000000000000000d0s0 c3t600A0B80002FA60C0000000000000000d0s4 c3t600A0B80002FA5F50000000000000000d0s1 ... (6 Replies)
Discussion started by: sleepy_11
6 Replies

4. Solaris

FSCK root file system (/dev/vx/dsk/bootdg/rootvol)

Hi, I need to fsck the root file system on my Solaris 9 server. It is a UFS file system but it is under Veritas control. I want to know which fsck I need to use to check the file system. The default Solaris fsck (/usr/sbin/fsck) or the Veritas (/lib/fs/vxfs/sparcv9/fsck) fsck? I take it I... (3 Replies)
Discussion started by: gwhelan
3 Replies

5. Solaris

How do I determine the hard drives in /dev/dsk in OpenSolaris?

I have a Solaris machine running OpenSolaris v5.11. It came with a hard drive. It's called /dev/dsk/c4d0s0. I added two new hard drives into the box. I can't figure out what it's called in /dev/dsk. There are 210 filenames in /dev/dsk. How do I find out which filename corresponds to the... (2 Replies)
Discussion started by: sqa777
2 Replies

6. UNIX for Dummies Questions & Answers

Meaning of mount /dev/dsk/c... /mnt

Hi May I know the meaning of the following command mount /dev/dsk/c1t0d0s3 /mnt Will I be able to use my tape drive after that? Thanks (3 Replies)
Discussion started by: rahmantanko
3 Replies

7. Solaris

how to make less capacity /dev/dsk/c1t0d0s5

how to make less capacity on /dev/dsk/c1t0d0s5 Filesystem size used avail capacity Mounted on /dev/dsk/c1t0d0s0 9.6G 2.3G 7.2G 25% / /dev/dsk/c1t0d0s1 9.6G 4.1G 5.4G 44% /usr /dev/dsk/c1t0d0s4 9.6G 81M 9.4G 1% /var... (1 Reply)
Discussion started by: Cah.Lanang
1 Replies

8. Solaris

Size missing on /dev/dsk/c0t0d0s3

Our used size is 83 gb. Total of the folders and documents size is46,2 gb. 83-46=37 gb. Where is my space. Where was lost? Could you please I need your opinions? {root}/space>du -s -h * 308K alaerrm-jprof 1K argerela 20G baerckup_in 1.8G cererm 28M ecerlipselink ... (8 Replies)
Discussion started by: getrue
8 Replies

9. Solaris

Canīt open /dev/dsk/c1t0d0s0 Clone/mirror

Hello friends, I Working with Solaris 8 on a SunFireV890, 150 GB SCSI HD's in Raid 1 (mirroring), my problem is that the master disk failed and going to put the slave (mirror) as a Master in the slot 0 (SCSI) will not start. The original mounting this, mirror in Raid 0: c1t0d0s0 (master)... (10 Replies)
Discussion started by: grymorum
10 Replies

10. Solaris

Lun remove, stuck in /dev/dsk and /dev/rdsk

So, we removed a LUN from the SAN and the system is refusing to remove the references to it in the /dev folder. I've done the following: devfsadm -Cv powermt -q luxadm -e offline <drive path> luxadm probe All those commands failed to remove the path. The drive stills shows up as <drive... (13 Replies)
Discussion started by: DustinT
13 Replies
DISKLABEL(8)						    BSD System Manager's Manual 					      DISKLABEL(8)

NAME
disklabel -- read and write disk pack label SYNOPSIS
disklabel [-ACDFrtv] disk disklabel -e [-CDFIrv] disk disklabel -i [-DFIrv] disk disklabel -R [-DFrv] disk protofile disklabel -w [-DFrv] [-f disktab] disk disktype [packid] disklabel [-NW] disk disklabel -l DESCRIPTION
disklabel can be used to install, examine, or modify the label on a disk drive or pack. When writing the label, it can be used to change the drive identification, the disk partitions on the drive, or to replace a damaged label. The -e, -i, -l, -R, -w, -N, and -W options determine the basic operation. If none are specified the label is displayed. -e Edit the existing label (using EDITOR) and write it back to the disk. If EDITOR is undefined, then vi(1) is used. -i Interactively update the existing label and write it back to the disk. -l Show all known file system types (those that can be specified along a partition within the label) and exit. -R Write (restore) a label by reading it from protofile. The file should be in the same format as the default output. -w Write a standard label for the specified disktype. See disktab(5). -N Disallow writes to the disk sector that contains the label. This is the default state. -W Allow writes to the disk sector that contains the label. This state may not persist if no programs have the disk open. The majority of the rest of the options affect more than one form of the command: -A Read all labels from the disk, including ones deleted with disklabel -D. Implies -r. -C Output the partition offset and size values in <cylinder/head/sector> format. Note this format is always accepted on input with either the -e or -R flags. -D Delete all existing labels (by 1's complementing the magic number) before writing any labels to their default location. Implies -r. If -D is specified without a request to write the label, then existing labels are just deleted. -F Treat disk as a regular file. This suppresses all ioctl(2) calls, and is the default if disk is a regular file. disk is always opened using opendisk(3) even if -F is specified. Implies -r. -I If a label cannot be read from disk request the default one from the kernel. Implies -r. -f disktab Specify the name of a file to use instead of /etc/disktab. -r Read/write the disk directly rather than using ioctl(2) requests on the kernel. When writing a label, the kernel will be told about the label before the label is written and asked to write afterwards. This is the historic behaviour and can be supressed by specifying -F. -t Format the output as a disktab(5) entry. -v Be verbose about the operations being done, in particular the disk sectors being read and written. Specifying -v more than once will increase the verbosity. On systems that expect to have disks with MBR partitions (see fdisk(8)) disklabel will find, and update if requested, labels in the first 8k of type 169 (NetBSD) MBR labels and within the first 8k of the physical disk. On other systems disklabel will only look at the start of the disk. The offset at which the labels are written is also system dependent. disklabel will detect byteswapped labels, but currently cannot display them. Previous versions of disklabel could update the bootstrap code on some architectures. This functionality has been subsumed by installboot(8). FILES
/etc/disktab EXIT STATUS
The exit status of disklabel is set to indicate any errors or warnings. The values used are: 0 The disklabel utility has completed successfully. 1 A fatal error has occurred, such as unknown options passed on the command line, or writing the disklabel failed. 4 An I/O error of some sort occurred. 101..n One or more warnings occured while reading the disklabel. Subtract 100 to get the number of warnings detected. EXAMPLES
disklabel sd0 Display the in-core label for sd0 as obtained via /dev/rsd0c. disklabel -i -r sd0 Read the on-disk label for sd0, edit it using the built-in interactive editor and reinstall in-core as well as on-disk. disklabel -i -I sd0 As previous, but don't fail if there was no label on the disk yet; provide some default values instead. disklabel -e -I sd0 As previous, only edit using $EDITOR disklabel -w -r /dev/rsd0c sd2212 foo Create a label for sd0 based on information for ``sd2212'' found in /etc/disktab, using foo as the disk pack label. If you do not have an entry for your disk in /etc/disktab, you can use this style to put an initial label onto a new disk. Then dump the label to a file (using disklabel sd0 > protofile), editing the file, and replacing the label with disklabel -R sd0 protofile. disklabel -R sd0 mylabel Restore the on-disk and in-core label for sd0 from information in mylabel. DIAGNOSTICS
The kernel device drivers will not allow the size of a disk partition to be decreased or the offset of a partition to be changed while it is open. Some device drivers create a label containing only a single large partition if a disk is unlabeled; thus, the label must be written to the ``a'' partition of the disk while it is open. This sometimes requires the desired label to be set in two steps, the first one creating at least one other partition, and the second setting the label on the new partition while shrinking the ``a'' partition. SEE ALSO
opendisk(3), disklabel(5), disktab(5), dkctl(8), fdisk(8), gpt(8), installboot(8), mbrlabel(8), mscdlabel(8) BUGS
The disklabel structure stored on disk cannot support partitions/disks greater than 2TB. Please use gpt(8) and dkctl(8) to manage partitions and disks larger than 2TB. If the disk partition is not specified in the disk name (i.e., xy0 instead of /dev/rxy0c), disklabel will construct the full pathname of the disk and use the ``d'' partition on i386, hpcmips, or arc, and the ``c'' partition on all others. On the sparc, sparc64, sun2, and sun3 NetBSD systems, the size of each partition must be a multiple of the number of sectors per cylinder (i.e., each partition must be an integer number of cylinders), or the boot ROMs will declare the label invalid and fail to boot the system. In addition, the -r option should never be used on a sparc, sparc64, sun2, or sun3 system boot disk - the NetBSD kernel translates the NetBSD disk label into a SunOS compatible format (which is required by the boot PROMs) when it writes the label. Using the -r flag causes disklabel to write directly to disk, and bypass the format translation. This will result in a disk label that the PROMs will not recognize, and that therefore cannot be booted from. BSD
July 25, 2011 BSD
All times are GMT -4. The time now is 10:50 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy