On Mon, 9 Jul 2012 19:34:07 +0200 Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx> wrote: > Hi Neil, > > please see one comment below. > > On Mon, Jul 09, 2012 at 11:40:22AM +1000, NeilBrown wrote: > [...] > > The mount system call will notice that the device is read-only, and will make > > assume the read-only mount option. > > OK, so it should work as expected. > > The story was this. > After fixing the RAID-5 superblock problem, we > wanted to see if the filesystem was still OK. > So we started the RAID in r/o mode (so to avoid > any possible further damage from mount) and then > mounted the filesystem (actually, now that I > think of it, there was an LVM layer in the middle). > This mount caused a kernel error report (I do > not know if BUG() or else). > > Is there any explanation for that? Probably LVM isn't detecting that the underlying device is readonly and so forcing the upper device to be readonly. md doesn't do this either - it should. NeilBrown
Attachment:
signature.asc
Description: PGP signature
