Hi, On Tue, 30 Dec 2008 14:19:53 +0100, [email protected] wrote: > Hi, > I am experimenting with nilfs2 for a while now, because I like the > Idea of this filesystem. The filesystem I have problems with now is > a more complex problem. I used just for testing purpose a file on an > ext3 filesystem as a cryptoloop device and I used nilfs2 on the > loopback device. It worked for about half a year without a > problem. But I have no Idea what was actualy going wrong (ext3 > problem, cryptoloop problem, nilfs problem?) and I don't know if a > filesystem under normal conditations get corrupted like this > (actualy no real data loss either, because almost all files existed > elswhere) > But when I now try to mount the nilfs2 filesystem it does not > work. No result from the mount command, but the attached in > dmsg.
Thank you for reporting the problem. Again, it seems that a btree corruption happened. Sorry, but it's hard to track the cause directly from the stack dump. According to the log, the write barrier is disabled (it may be a restriction of cryptoloop). If you met an unexpected system down before mounting nilfs, please let me know. >The system is still useable, but I am not able to shut it down (have >to hold power button 3 seconds). And I am not able to unload the >nilfs module either (is in use) Hope this helps to further improve >nilfs2. robinx99 I've modified btree lookup routines to avoid system freeze and allow clean termination; I pushed it to our git repository. Regards, Ryusuke _______________________________________________ users mailing list [email protected] https://www.nilfs.org/mailman/listinfo/users
