Sponsored Content
Operating Systems Solaris FSCK root file system (/dev/vx/dsk/bootdg/rootvol) Post 302260061 by pupp on Wednesday 19th of November 2008 02:22:58 PM
Old 11-19-2008
this should do it

Code:
fsck -F vxfs -o full,nolog /dev/vx/rdsk/bootdg/rootvol

 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

sar + sdXY,Z + /dev/dsk

Hello! When I use "sar -d" I get information about disk activities like: sd0 ... sd0,a ... sd0,b ... ..... sd22 ... sd22,a ... ..... How I can find by , for example sd22,a , what physical disk is it. For example /dev/dsk/c1t3d0s1 easy to read and I can find by it physical disk.... (4 Replies)
Discussion started by: Colf
4 Replies

2. 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

3. 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

4. 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

5. UNIX for Dummies Questions & Answers

Run fsck on root file system

If i run fsck on one filesystem and fsck need to repair some things then this partition must be unmounted correct ? So running fsck on root file system isn't possible within same OS ? correct ? What is the best way to do that, live cd ? BR, Jurif (5 Replies)
Discussion started by: jurif
5 Replies

6. 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

7. Solaris

Not able to run fsck on root file system

I am trying to root disk mirroring on SunFire V210 Server. There are two disks on this server c1t0d0 and c1t1d0 . I completed all the steps and I updated the vfstab file too. After I have updated the vfstab file I run df -h command but could not see the changes i made in vfstab. Suddenly the server... (1 Reply)
Discussion started by: newbi8321
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

unable to repair the / filesystem. Run fsck manually (fsck -F ufs /dev/rdsk/c1t0d0s0)

What can I fix this issue? I have ran below commands but everything is same.:confused: WARNING: Last shutdown is later than time on time-of-day chip: check date. The / file system (/dev/rdsk/c1t0d0s0) is being checked WARNING - unable to repair the / filesystem. Run fsck manually (fsck -F... (4 Replies)
Discussion started by: getrue
4 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
fsck_pcfs(1M)						  System Administration Commands					     fsck_pcfs(1M)

NAME
fsck_pcfs - file system consistency check and interactive repair SYNOPSIS
fsck -F pcfs [generic_options] special fsck -F pcfs [generic_options] [-o specific_options] special DESCRIPTION
The fsck utility audits and interactively repairs inconsistent conditions on file systems. special represents the character special device on which the file system resides, for example /dev/rdiskette. The character special device, not the block special device, should be used. In the case of correcting serious inconsistencies, by default, fsck asks for confirmation before making a repair and waits for the operator to respond either yes or no. If the operator does not have write permission on the file system, fsck defaults to a -n (no corrections) action. See fsck(1M). Repairing some file system inconsistencies may result in loss of data. The amount and severity of data loss may be determined from the diagnostic output. When executed with the verify option (-o v), fsck_pcfs automatically scans the entire file system to verify that all of its allocation units are accessible. If it finds any units inaccessible, it updates the file allocation table (FAT) appropriately. It also updates any effected directory entries to reflect the problem. This directory update includes truncating the file at the point in its allocation chain where the file data is no longer accessible. Any remaining accessible allocation units become orphaned. Orphaned chains of accessible allocation units are, with the operator's concurrence, linked back into the file system as files in the root directory. These files are assigned names of the form fileNNNN.chk, where the Ns are digits in the integral range from 0 through 9. After successfully scanning and correcting any errors in the file system, fsck displays a summary of information about the file system. This summary includes the size of the file system in bytes, the number of bytes used in directories and individual files, and the number of available allocation units remaining in the file system. OPTIONS
generic_options The following generic options are supported: -m Check but do not repair. This option checks that the file system is suitable for mounting, return- ing the appropriate exit status. If the file system is ready for mounting, fsck displays a message such as: pcfs fsck: sanity check: /dev/rdiskette okay -n | -N Assume a no response to all questions asked by fsck; do not open the file system for writing. -V Echo the expanded command line, but do not execute the command. This option may be used to verify and to validate the command line. -y | -Y Assume a yes response to all questions asked by fsck. -o specific_options Specify pcfs file system specific options in a comma-separated list, in any combination, with no intervening spa- ces. v Verify all allocation units are accessible prior to correcting inconsistencies in the metadata. p Check and fix the file system non-interactively (preen). Exit immediately if there is a problem requiring intervention. w Check writable file systems only. FILES
special The device which contains the pcfs. The device name for a diskette is specified as /dev/rdiskette0 for the first diskette drive, or /dev/rdiskette1 for a second diskette drive. A hard disk device or high-capacity removable device name much be qualified with a suffix to indicate the proper FDISK partition. For example, in the names: /dev/rdsk/c0t0d0p0:c and /dev/rdsk/c0t4d0s2:c, the :c suffix indicates the first parti- tion on the disk contains the pcfs. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ |ATTRIBUTE TYPE |ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWesu | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ SEE ALSO
fsck(1M), fstyp(1M), fdisk(1M), mkfs(1M), mkfs_pcfs(1M), mountall(1M), attributes(5), pcfs(7FS), WARNINGS
The operating system buffers file system data. Running fsck on a mounted file system can cause the operating system's buffers to become out of date with respect to the disk. For this reason, the file system should be unmounted when fsck is used. If this is not possible, care should be taken that the system is quiescent and that it is rebooted immediately after fsck is run. Quite often, however, this is not suf- ficient. A panic will probably occur if running fsck on a file system modifies the file system. SunOS 5.10 28 Jan 2000 fsck_pcfs(1M)
All times are GMT -4. The time now is 01:49 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy