On Mon, Jan 22, 2018 at 2:06 PM, Claes Fransson <claes.v.fransson@xxxxxxxxx> wrote: > Hi! > > I really like the features of BTRFS, especially deduplication, > snapshotting and checksumming. However, when using it on my laptop the > last couple of years, it has became corrupted a lot of times. > Sometimes I have managed to fix the problems (at least so much that I > can continue to use the filesystem) with check --repair, but several > times I had to recreate the file system and reinstall the operating > system. > > I am guessing the corruptions might be the results of unclean > shutdowns, mostly after system hangs, but also because of running out > of battery sometimes? I think it's something else because I intentionally and unintentionally do unclean shutdowns (I'm really impatient and I'm a saboteur) on my laptop and I never get corruptions. In 18 months with an HP Spectre which doesn't even have ECC memory, and has an NVMe drive, *and* really remarkable for almost half this time I used the discard mount option which pretty much instantly obliterates unused roots, even when referenced in the super block as backup roots - and yet still zero corruption. No complaints on mount, scrub, or readonly checks. *shrug* Anyway I suspect hardware or power issue. Or even SSD firmware issue. > Furthermore, the power-led has recently started blinking (also when > the power-cable is plugged in), I guess because of an old and bad > battery. Maybe the current corruption also can have something to do > with this? However I almost always run with power cable plugged in in > last year, only on battery a few seconds a few times when moving the > laptop. > > Currently, I can only mount the filesystem readonly, it goes readonly > automatically if I try to mount it normally. Btrfs is confused and doesn't want to make the corruption worse. > > Fstab mount options: noatime,autodefrag (I have been using the option > nossd with older kernels one period in the past on the filesystem). > > If it matters, I have been running duperemove many times on the > filesystem since creation. I don't think it's related. > > To test the RAM, I have been running mprime Blend-test for 24 hours > after the corruption without any error or warning. I'm not familiar with it, pretty sure you want this for UEFI: https://www.memtest86.com/download.htm Where you can use that or memtest86+ if the firmware is BIOS based. > I have never noticed any corruptions on the NTFS and Ext4 file systems > on the laptop, only on the Btrfs file systems. NTFS and ext4 likely won't notice such corruptions either (although new ext4 volumes any day now will have checksummed metadata by default) as they're weren't designed with such detection in mind. -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
