The umount *has* to complete, even if the f/s is broken - else you can't fix it. Well, you could try, but let's not go there. Of course, what a fsck treats as "fixed" and what we as users might like to think it produces may be totally at odds. Truncating files and unlinking inodes ain't my idea of fixing anything. The sooner btrfs gets production ready the better.
Shane ... On Fri, Feb 26th, 2010 at 4:18 AM, "Harder, Pieter" wrote: > Ron, > > I don't know if the problem is with Reiser per sé. I also run SAP on > Reiser on SLES10 SP3. Never saw your kind of problem there. But I > have seen your problem (dirty filesystems after clean, verified > (=executed manually) umount) on our TSM server. And that one is > totally on EXT3. In the end all filesystems rely on the blockio > service doing what it tells it does ;-) If not, anything can happen. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
