I see, I'll follow what you said. Thanks. Btw, what could be the source of the error so that I may avoid it in the future? And would deleting the offending file (if the error is tied to one) also remove the error? On Sat, May 26, 2012 at 10:49 PM, Christian Smith <csmith@xxxxxxxxxxxxxxxxxxxxxxxx> wrote: > On Sat, May 26, 2012 at 02:15:41AM +0800, Kenneth Langga wrote: >> It's a 3TB harddisk. Could that be the reason? >> >> Right now, it's mounted read-only. Is it safe to make it read/write >> again? And can I run nilfs-clean on it and maybe the error would be >> gone? >> > > You should be able to remount read/write, as you'll still have your > old snapshots or checkpoints to mount from instead if it all goes > wrong. > > In my experience, though, once the clearner fails to be able to > clean segments due to logical errors, it's game over and a > backup/mkfs/restore is needed. But then, I mostly run NIFLS on > small slow SDD, so that's no great hardship. We desperately need > a fsck to handle scenarios like that. > > I can't see the size of the disk being a problem. All the data > pointers are 64-bit, so should comfortably handle 3TB. > > In short, try read-write, but be prepared to reformat. > > Also, if you're using a 3TB disk for NILFS to store media > files, I'd perhaps suggest against it, if not for the reason > that backup/restore on that much data will take an age. I > currently stick to nilfs for my root filesystems, leaving > big and/or personal data on more stable, less cutting edge > filesystems. > > Christian -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
