On 12 April 2018 at 00:25, Qu Wenruo <quwenruo.btrfs@xxxxxxx> wrote: > I'm curious about what's the underlying disk? It's an Samsung PM951 NVMe SSD. > Is it plain physical device? Or have other layers like bcache/lvm? btrfs on LUKS >> btrfs check > Full output please. https://gist.githubusercontent.com/tlvince/acf51b37622c216e1c33cdc3dfbd321f/raw/d0237948bbffacd4bb8d53fdfa5f23391416c1e2/btrfs-check.txt > For transid error, btrfs check --repair can fix it, but only do it when > that's the only problem. I ran this (for ~12+ hours) to no avail; it appears to have been looping around "Btree for root 259 is fixed". I grew impatient and SIGINT-ed, which unsurprisingly toasted the file system once and for all (I rebuilt from backups at that point). Full output: https://gist.githubusercontent.com/tlvince/8060c19526aa011b0baff2b12e3873fd/raw/ecc43bd9dc7b352e490aa0bf0deac368af04e117/btrfs-check-repair.txt Note, the system was fine for a few days after zero-log (before check --repair), but then hit the same transid error at boot. On 13 April 2018 at 06:46, Duncan <1i5t5.duncan@xxxxxxx> wrote: > What mount options? In particular, is the discard option used (and of > course I'm assuming nothing as insane as nobarrier)? noatime,compress=lzo ... as well as some defaults: rw,noatime,compress=lzo,ssd,space_cache -- 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
