Hi, > I will now watch the nilfs2 device fill up to see what happens and will > report back soon.
this went better than I thought. nilfs2 is still online, simply reporting disk full. Linux RAID marked the remote loop device as faulty and continued. I removed them with mdadm. losetup could unload them as well. Nothing ugly happened. What I learned in the process is that lscp is painfully slow when there are many checkpoints to report. In my case, two weeks worth with one cp every 5 secs (database traffic is really worst case for any filesystem) took about 20 minutes to dump. 10 mb. This is nilfs-utils 2.0.6 - maybe this is fixed in a later release? Anyway, my nilfs was running without cleanerd and that has to have some downsides. Space filled up very quickly, which leads me to a more realistic approach in which the remote loop file will be added to do backup, then removed again. Maybe once an hour or every ten minutes, or daily - depending on how much space one can spend on backup and how much is moving on the indestructible block device. Of course it would be much much more efficient to have a block device designed to do logging without loop and nilfs2 below, but I haven't seen anything like that yet. So for now, creating an indestructible block device is a fun thing to do and provides a backup solution with features way beyond most backup software out there. Good: * incremental block-level backup * point-in-time recovery for both, single files and complete volume * works via network, so off-site is possible * real-time backup Bad: * No cleanerd for this - have to replace volumes by hand * Much backup-space overhead * Probably lots of traffic * No warranty whatsoever, ymmv So far, Pierre Beck _______________________________________________ users mailing list [email protected] https://www.nilfs.org/mailman/listinfo/users
