Re: btrfs on top of bcache on top of dmcrypt on top of md raid5

2016-02-14 Thread Chris Murphy
Use all defaults for everything. Anything new by show should do the right thing including 4096 byte alignment. gargamel:~# cryptsetup luksDump /dev/md8 [snip] Payload offset: 3072 This is a bit weird because the default is 4096. But because the LUKS offset (header + payload + extra unused space)

Re: btrfs on top of bcache on top of dmcrypt on top of md raid5

2016-02-14 Thread Marc MERLIN
On Sun, Feb 14, 2016 at 01:43:05PM -0700, Chris Murphy wrote: > Use all defaults for everything. Anything new by show should do the > right thing including 4096 byte alignment. > > gargamel:~# cryptsetup luksDump /dev/md8 > [snip] > Payload offset: 3072 > > This is a bit weird because the

btrfs on top of bcache on top of dmcrypt on top of md raid5

2016-02-12 Thread Marc MERLIN
I have a 5 drive md array with dmcrypt on top, and btrfs on top of that. Kernel: 4.4 but the filesystem was created 2 years ago with an older version of btrfs. It's littered with files and hardlinks (it's a backup server). Mostly it gets btrfs receive data, and rsyncs of filesystem trees that are