Re: Cant find sunit and swidth on luks encrypted raid6 device

[Eric Sandeen <sandeen@sandeen.net>]

Eric Sandeen wrote:

> What does "blockdev --getsize64" and "blockdev --getsize" and/or
> /proc/partitions say about how big /dev/mapper/raid6 is?
> 
> Can you use dd to write to the last 128k of the device, as reported by
> blockdev --getsize64?

Not a cryptsetup problem, FWIW:

[root@inode obj]# /tmp/truncate fsfile 7000893943808
Truncating fsfile to 7000893943808
[root@inode obj]# ls -l fsfile
-rw-r--r-- 1 root root 7000893943808 Sep 19 17:23 fsfile
[root@inode obj]# mkfs.xfs -f fsfile
meta-data=fsfile                 isize=256    agcount=32,
agsize=53412581 blks
         =                       sectsz=512   attr=0
data     =                       bsize=4096   blocks=1709202592, imaxpct=25
         =                       sunit=0      swidth=0 blks, unwritten=1
naming   =version 2              bsize=4096
log      =internal log           bsize=4096   blocks=32768, version=1
         =                       sectsz=512   sunit=0 blks, lazy-count=0
realtime =none                   extsz=4096   blocks=0, rtextents=0
2b2d4c133680: Badness in key lookup (length)
bp=(bno 13673620728, len 131072 bytes) key=(bno 13673620728, len 4096 bytes)

If we take out the pwrite that does the end-of-device zeroing, we don't
get the error... but that's been there since forever, so again, I'm a
bit confused here.

-Eric