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
dskx(8) System Manager's Manual dskx(8)
Name
dskx - generic disk exerciser
Syntax
/usr/field/dskx [ options ] -rdev
/usr/field/dskx [ options ] -pdevpart
/usr/field/dskx [ options ] -cdev
Description
The exerciser tests the disk drives on your system. The exerciser has three main options which include read only, write/read/validate data
on a partition, and write/read/validate data of a disk.
The exerciser does random seeks and reads of random block sizes and random seeks, writes, reads, and validations of random data patterns of
random block sizes. The exerciser will run until or kill -15 pid is sent to the process.
A logfile is made in for you to examine and then remove. If there are errors in the logfile, make sure you check the file, because that is
where the driver and kernel error messages are saved.
CAUTION: Both the -c and -p options of the exerciser destroy data on the disk. Use extreme caution before using them on any non-scratch
media. If you are unsure of what data is on the disk, contact your system manager before running with either of these options.
Arguments
One of the following function flags and arguments must be specified.
-rdev Performs a random read-only test on all partitions except the c partition. The dev argument can be a raw or buffered device name
and number. For example, rhp0, ra3, hk1.
-pdevpart Writes, reads, and validates data from the device name and number specified by dev and the partition specified by part. The dev
argument can be a raw or buffered device name and number. For example, rhp0, ra3, hk1. The part argument can be any valid par-
tition from a - h.
CAUTION: Be careful when exercising partitions that overlap other partitions, as you may inadvertently destroy data on a parti-
tion that you do not want to test. You can use the -q option of the command to see what partitions overlap on the device on your
system.
-cdev Writes, reads, and validates data from all partitions except the c partition on the device specified by dev. The dev argument
can be a raw or buffered device name and number. For example, rhp0, ra3, hk1.
Options
The options are:
-h Prints help message for the command.
-ofile Saves output diagnostics in file.
-tn Specifies the run time in minutes (n). The default is to run until the process receives a or kill -15 pid.
-dm Prints statistics every m minutes.
Restrictions
If there is a need to run a system exerciser over an NFS link or on a diskless system there are some restrictions. For exercisers that
need to write into a file system, such as the target file system must be writable by root. Also the directory, in which any of the exer-
cisers are executed, must be writable by root because temporary files are written into the current directory. These latter restrictions
are sometimes difficult to overcome because often NFS file systems are mounted in a way that prevents root from writing into them. Some of
the restrictions may be overcome by copying the exerciser to another directory and then executing it.
Examples
The following example exercises RA disk unit 1, for 60 minutes in the background:
% /usr/field/dskx -t60 -cra1 &
The following example exercises raw HP disk unit 0, partition d, until or kill -15 pid:
% /usr/field/dskx -prhp0d
See Also
Guide to System Exercisers
dskx(8)