Apparent fsck failure ...

Apparent fsck failure ...

[Bill Wilken]

I am running Suse 9.3, 32-bit, on an Athlon-64 CPU (my 2800-series cpu
won't support the 64-bit product) with 1GB RAM, a 40GB hard drive
(dev/hda2), and a DVD/RW.  Suse tells me that I must run fsck manually
because dev/hda2 is mounted with write permissions (See below) Why
wouldn't you mount a hard drive partition with write permissions?

linux:/home/wilkenw # fsck -CV
fsck 1.36 (05-Feb-2005)
Checking all file systems.
[/sbin/fsck.reiserfs (1) -- /] fsck.reiserfs /dev/hda2
reiserfsck 3.6.18 (2003 www.namesys.com)

*************************************************************
** If you are using the latest reiserfsprogs and  it fails **
** please  email bug reports to reiserfs-list@namesys.com, **
** providing  as  much  information  as  possible --  your **
** hardware,  kernel,  patches,  settings,  all reiserfsck **
** messages  (including version),  the reiserfsck logfile, **
** check  the  syslog file  for  any  related information. **
** If you would like advice on using this program, support **
** is available  for $25 at  www.namesys.com/support.html. **
*************************************************************

Will read-only check consistency of the filesystem on /dev/hda2
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you
do):Yes
###########
reiserfsck --check started at Thu Aug 18 15:00:39 2005
###########
Partition /dev/hda2 is mounted with write permissions, cannot check it
fsck.reiserfs /dev/hda2 failed (status 0x10). Run manually!

Re: Apparent fsck failure ...

[michael chang]

On 8/18/05, Bill Wilken <bill.wilken@comcast.net> wrote:
> because dev/hda2 is mounted with write permissions (See below) Why
> wouldn't you mount a hard drive partition with write permissions?

Because then something can write to the partition when fsck is
working.  Solution? Remount read only.

Same with ext2/3 and everything else, IIRC....

-- 
~Mike
 - Just my two cents
 - No man is an island, and no man is unable.

Re: Apparent fsck failure ...

[Bill Wilken]

Thanks.  You jogged my memory.  Coming back to the unix world after a
long absence.  If I remember correctly, under Altos Unix 20 years ago,
you could simply bring up the system in single-user mode and avoid the
need to remount the partition read/only.