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? Thanks, bye, -- piergiorgio -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
