11-28-2011
Fsck with SVM
Hello
I want to ask that how to mount and run fsck in SVM disk.In my scenario if i have to disks c0t0d0 and c0t1d0 these two disks are in Mirroring (raid1) if i want to run fsck on the disks than below are the right steps?
ok boot cdrom -s
mount /dev/dsk/c0t0d0s0 /a
cd /a
fsck /dev/rdsk/c0t0d0s0
Question 1: Can i run the fsck on both disks here or the first one only?
ok boot cdrom -s
mount /dev/md/dsk/c0t0d0s0 /a
cd /a
fsck /dev/md/rdsk/c0t0d0s0
kindly tell me which one is the right option or step by step guide will be appreciated thanks in advance.
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Once in a while, I would think it advisable to run fsck -y to check the disk.
Should I sign in as su or sudo?
What is the difference and which is preferred?
Thank you in Advance! (4 Replies)
Discussion started by: rpatrick
4 Replies
2. Solaris
OS: Solaris 5.8
Everytime I run fsck -y I get: FILE SYSTEM STATE IN SUPERBLOCK IS WRONG; FIX? yes
Do I need to run fsck with the backup superblock option or is there
some other option I should use. I have tried the format->analyze->read
option but that does not report any corrupt blocks.... (5 Replies)
Discussion started by: run_time_error
5 Replies
3. UNIX for Dummies Questions & Answers
I want to use fsck to check and repair my linux system. When I use this command, what do I need to pay attention to or what should I do to make job running successfully. Thanks for your inputs for a newbie. (3 Replies)
Discussion started by: duke0001
3 Replies
4. Solaris
Hello
I am getting this in dmesg:
/mount1: unexpected free inode 1262865, run fsck(1M) -o f
What are the options I should use with fsck?
thanks (2 Replies)
Discussion started by: melanie_pfefer
2 Replies
5. UNIX for Dummies Questions & Answers
i want to know what does it mean by doing a consistentcy check fsck on a disk and why journaling filesystems dont need to do it
and what is meant by disk is in a consistent state when writing because entries are recorded in a journal and then to the metadata and then removed from journal (1 Reply)
Discussion started by: farhan_t49
1 Replies
6. Solaris
I am not able to boot into solaris. I am getting following message.
The / file system (/dev/rdsk/c0t0d0s0) is being checked.
Warning - Unable to repair the / filesystem. Run fsck manually(fsck -F ufs /dev/rdsk/c0t0d0s0).
I ran fsck manually but it didn't work.
Help from anyone would be... (1 Reply)
Discussion started by: likhitgatagat
1 Replies
7. Solaris
Hi,
I am getting this error while server booting up, not sure how to fix this. Unable to mount these file systems
/dev/md/rdsk/d51: No such device or address
Can't open /dev/md/rdsk/d51: No such device or address
/dev/md/rdsk/d51: CAN'T CHECK FILE SYSTEM.
/dev/md/rdsk/d51: UNEXPECTED... (1 Reply)
Discussion started by: bobby320
1 Replies
8. Solaris
Hello Friends,
My doubt is
1) How do we know if we need Fsck to run or not
can we check using any switch so that we can know if our filesystem really requires to run fsck or not?? (2 Replies)
Discussion started by: saurabh84g
2 Replies
9. Solaris
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
Hi,
When we are running fsck in vxvm FS within few sec it will completed even if data is more than 500GB or in TB also.
compare to UFS FS in that it will take more time compare with vxvm.UFS check FS in block level. & then vvxm on where its checking the FS.
Please explain. (1 Reply)
Discussion started by: tiger09
1 Replies
LEARN ABOUT NETBSD
badsect
BADSECT(8) BSD System Manager's Manual BADSECT(8)
NAME
badsect -- create files to contain bad sectors
SYNOPSIS
badsect bbdir sector ...
DESCRIPTION
badsect makes a file to contain a bad sector. Normally, bad sectors are made inaccessible by the standard formatter, which provides a for-
warding table for bad sectors to the driver; see bad144(8) for details. If a driver supports the bad blocking standard it is much preferable
to use that method to isolate bad blocks, since the bad block forwarding makes the pack appear perfect, and such packs can then be copied
with dd(1). The technique used by this program is also less general than bad block forwarding, as badsect can't make amends for bad blocks
in the i-list of file systems or in swap areas.
On some disks, adding a sector which is suddenly bad to the bad sector table currently requires the running of the standard DEC formatter.
Thus to deal with a newly bad block or on disks where the drivers do not support the bad-blocking standard badsect may be used to good
effect.
badsect is used on a quiet file system in the following way: First mount the file system, and change to its root directory. Make a directory
BAD there. Run badsect giving as argument the BAD directory followed by all the bad sectors you wish to add. The sector numbers must be
relative to the beginning of the file system, but this is not hard as the system reports relative sector numbers in its console error mes-
sages. Then change back to the root directory, unmount the file system and run fsck(8) on the file system. The bad sectors should show up
in two files or in the bad sector files and the free list. Have fsck(8) remove files containing the offending bad sectors, but do not have
it remove the BAD/nnnnn files. This will leave the bad sectors in only the BAD files.
badsect works by giving the specified sector numbers in a mknod(2) system call, creating an illegal file whose first block address is the
block containing bad sector and whose name is the bad sector number. When it is discovered by fsck(8) it will ask ``HOLD BAD BLOCK ?'' A
positive response will cause fsck(8) to convert the inode to a regular file containing the bad block.
DIAGNOSTICS
badsect refuses to attach a block that resides in a critical area or is out of range of the file system. A warning is issued if the block is
already in use.
SEE ALSO
bad144(8), fsck(8)
HISTORY
The badsect command appeared in 4.1BSD.
BUGS
If more than one of the sectors in a file system fragment are bad, you should specify only one of them to badsect, as the blocks in the bad
sector files actually cover all the sectors in a file system fragment.
BSD
June 5, 1993 BSD