Hello Lukáš, > Currently I do not think there is a way to check whether mounted > file system contains errors (EXT2_ERROR_FS flag is set in super > block). > > You either have to check the logs, or run fsck before mounting the > file system. > > It really seems like a optimal thing to provide a way to inform user > space about this without the need to parse the log. I think that > sysfs is a perfect place for this. > > However we might to go a step further, because I do not > really like the idea of allowing to mount the file system with > errors by default. It does not really make sense to me and I wonder > whether someone actually intend to do it this way. > > What about having this scenario respect "errors=" setting ? Of > course it might not make sense to panic when mounting file system > with errors with "errors=panic" option, we can just fail the mount. > > Will that help your case ? Yes for some cases, no for others :) For example I do not want server to fail booting if it could otherwise start (even though it might need some intervention, at least running fsck). Giving simple way (like mentioned sysfs access) would make monitoring such issues much simpler. Of course for some cases, it's for sure safer to disallow mounting rather then risking further data corruption... I'm not sure how big is chance that mounting filesystem with errors can cause more errors, I guess it depends on the nature of the problem.. cheers! nik > > Thanks! > -Lukas > -- ------------------------------------- Ing. Nikola CIPRICH LinuxBox.cz, s.r.o. 28.rijna 168, 709 00 Ostrava tel.: +420 591 166 214 fax: +420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: servis@xxxxxxxxxxx -------------------------------------
Attachment:
pgpj_w16XjeTs.pgp
Description: PGP signature
