11-18-2014
That's rather contradictory, like asking for a bluer orange. If it were possible, it would end up being an even bigger hassle and risk than just unmounting it -- imagine losing 30 minutes of live changes on a corrupted and unrecoverable disk once you've realized "whoops, I really shouldn't have been writing to that". Mounting a bad filesystem read-write may have problems other than corruption -- it could work fine, for example, with one important file missing that you don't realize until later, after it's long past recoverable.
The closest you can do to what you want is mounting it read-only. Actually fixing it while it's mounted, read-only or not, is of course a recipe for a kernel panic.
I suppose it might also be possible at the disk level. Remove one mirror or something and scan it. You'll want to have it unmounted, or mounted read-only, while you do so. Again, though, you don't want to be writing changes to a disk that might be bad; you could lose your current changes.
Or some sort of scratch-disk union mount, so you're saving new changes in a temporary space until you've verified the disk is okay. Merging the two partitions would be difficult though.
I can't think of anything that's faster and less trouble than just doing the job properly in the first place. You can't re-bore your engine while it's running.
Last edited by Corona688; 11-18-2014 at 02:06 PM..
This User Gave Thanks to Corona688 For This Post:
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 have a Solaris 7 box. We got a strange error in the syslog, which read as follows:
Nov 15 11:50:16 server-01 unix: NOTICE: free inode /mount1/8025691 had size 0x20d
I consulted with a fellow sysadmin, and he suggested running "fsck -N" on the filesystem in question without unmounting it. So I... (1 Reply)
Discussion started by: GKnight
1 Replies
4. 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
5. 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
6. 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
7. UNIX for Dummies Questions & Answers
Hello
I own a SPARC Ultra 10 workstation (standalone) and when issuing the fsck command I get the following output on fs C0t0d0s7:
Phase 1 (checks blocks and sizes):
dada warning: /pci@lf;0/pci@1, 1/ide@3/dad@0,0(dad1): ATA Transport failed:reason, `incomplete'>
Uncorrectable data... (2 Replies)
Discussion started by: tjwops
2 Replies
8. 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
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 ULTRIX
radisk
radisk(8) System Manager's Manual radisk(8)
Name
radisk - Digital Storage Architecture (DSA) disk maintenance
Syntax
/etc/radisk
radisk -c LBN length special
radisk -e special
radisk -n special
radisk -r LBN special
radisk -s LBN length special
Description
The Digital Storage Architecture (DSA) disk maintenance program provides the essential functions to manage DSA disk devices. The command
must be used on unmounted disk partitions to insure correct results.
The LBN is a decimal number that represents the logical block number as reported in the errorlog file. The LBN is the actual disk block
number starting from the beginning of the disk.
The length is a decimal number that indicates how many (512 byte) blocks to process. The length specified may be -1 to indicate the last
block of the specified partition.
The special file specified is used with -c, -e, -n, and -r options and indicates an unmounted c partition of a character device special
file.
Options
The following options may be set with
-c Clears a forced error indicator on the range of specified LBNs. The forced error condition indicates that the data in the disk block
is bad. The disk block is good, but the data can not be read without getting an error detection code (EDC) error. This option will
cause the forced error condition to be removed. After the forced error indicator is cleared, the EDC error will not be reported nor
will the data be marked as bad.
All indications that the data is corrupt are lost. The data should be restored either by manual methods or with the command. The com-
mand affects the integrity of the data on a disk and should be followed by a file system restore if data is affected.
-e Sets the exclusive access attribute associated with the specified disk. This attribute is provided by multihost controllers to
restrict access to a disk to one host. The command will return a failure status if the disk is already exclusively associated with
another host or the underlying controller does not provide multihost support. If the command is issued to a disk that is currently
mounted and the command fails, the disk will no longer be online to this host. For this reason the -e option should not be issued to
a disk that is mounted.
n Clears the exclusive access attribute associated with the specified disk. If the controller provides multihost support and the exclu-
sive access attribute is not set for a particular disk, it would be possible for the disk to be accessed by more than one host. The
command will return a failure status if the disk is not currently and exclusively associated with this host or the underlying con-
troller does not provide multihost support.
-r Replaces a block on the disk specified by LBN. See Restrictions.
-s Starts a scan for bad blocks on the specified area on a disk. Bad blocks are disk blocks that have data transfer errors to the extent
that they cannot be relied on. When a bad block is found, it is replaced and the bad block's LBN is reported. The LBN specified with
the option can be 0 to indicate the first block in the specified partition. If 0 is specified, however, the program starts searching
from the first block of the partition. The option will accept any valid partition on the disk. This allows any partition to be scanned
without scanning the entire disk and ensures that the specified partition is free of bad blocks. As an example, indicates the h parti-
tion of the third logical disk unit.
Diagnostics
The command generates messages when the user is not privileged, when the LBN is not in the specified partition, and when the length exceeds
the size of the partition.
Restrictions
You must be in single-user mode when using the and options of the program. If you are in multiuser mode, hangs the system and cannot be
killed. If this happens, you must reboot.
The option is supported only with those DSA disks which use host-initiated dynamic bad block replacement.
The and options are only supported on controllers that provide multi-host support. These options are only supported on HSC Version 5.00 or
later.
See Also
dkio(4), ra(4), sdc(4), chpt(8), mount(8), restore(8)
Guide to System Disk Maintenance
4th Berkeley Distribution radisk(8)