NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: misc/43905: fsck_root fails on write protected partition



The following reply was made to PR misc/43905; it has been noted by GNATS.

From: Christoph Badura <bad%bsd.de@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: misc/43905: fsck_root fails on write protected partition
Date: Sun, 26 Sep 2010 23:42:26 +0200

 On Sun, Sep 26, 2010 at 07:55:03PM +0000, Alan Barrett wrote:
 >  On Sat, 25 Sep 2010, bad%bsd.de@localhost wrote:
 >  > 1) fsck aborts because it can't get write access to the block device
 >  > even thought he file system is clean and it doesn't actually want to write
 >  > to the device anyway.
 >  
 >  /etc/rc.d/fsck_root invoked "fsck -p /" (assuming that fsck_flags had
 >  the default value of "-p").  Given that, it's not clear to me that fsck
 >  should have behaved any differently.
 
 How about "it should behave like TFM(tm) says"?  Or, alternitively "it should
 behave like it has the last 15+ years"?  That has worked satisfactorily
 for me.
 
 youll-thank-me-later!bad 109 % uname -r; grep xbd0a /etc/fstab; sudo fsck -p /
 5.1_RC4
 /dev/xbd0a      /       ffs     ro
 Password:
 /dev/rxbd0a: file system is clean; not checking
 
 fsck_flags is at the default value on both domUs.
 
 I don't know why that blows up on -current.  And I don't expect you to answer
 that.
 
 I don't know what fsck_root is for either.  Lacking any documentation at
 all it looks to me like it is trying to duplicate standard functionality.
 
 --chris
 


Home | Main Index | Thread Index | Old Index