Raimund Andersen wrote: > Eric Sandeen <sandeen <at> redhat.com> writes: > >> You should expect that checking a live filesystem will produce errors, >> actually. So don't worry about that. The filesystem is not quiesced, >> and it's not consistent. That is to be expected, and it's why you see >> the different behavior w/ forcefsck vs. e2fsck -n on the live fs. >> >> As for the spurious ENOSPC, I'm not certain. Do you still get the error? > > Thanks for your quick reply. No, at the moment, I don't get it. Yesterday, it > occured once and a reboot let it vanish, and I got it some days before. Also > then, a reboot let it disappear. So could it be of help if I collect any > information in the case it might reappear? What exactly should I do then? If you can, I'd test a 2.6.29-rc4 kernel, see if the very latest code is behaving any better... -Eric > Thank you, once again. > > rgds Raimund -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
