* Cant find sunit and swidth on luks encrypted raid6 device
@ 2007-09-19 18:29 Jochen K.
2007-09-19 19:40 ` Bhagi rathi
2007-09-19 19:42 ` Eric Sandeen
0 siblings, 2 replies; 10+ messages in thread
From: Jochen K. @ 2007-09-19 18:29 UTC (permalink / raw)
To: xfs
Hi,
I tried to create a xfs filesystem on a big encrypted mapped device but it
isnt working at all.
Also got latest kernel and kernel.org drivers for the raid controller.
I hope you guys have any idea what might have happened here :)
With ext3 its workin but i have no clue how to fix this problem.
Kernel: 2.6.22.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686 i686 i386
GNU/Linux
mdadm - v2.6.3 - 20th August 2007
cryptsetup 1.0.5
mkfs.xfs version 2.9.4
--added encryption--
/sbin/cryptsetup -c aes-cbc-essiv:sha256 -y -s 256 luksFormat /dev/md0
/sbin/cryptsetup luksOpen /dev/md0 raid6
[output without encryption]
mkfs.xfs /dev/md0
meta-data=/dev/md0 isize=256 agcount=32, agsize=53412608
blks
= sectsz=4096 attr=0
data = bsize=4096 blocks=1709202880, imaxpct=25
= sunit=32 swidth=448 blks, unwritten=1
naming =version 2 bsize=4096
log =internal log bsize=4096 blocks=32768, version=2
= sectsz=4096 sunit=1 blks, lazy-count=0
realtime =none extsz=1835008 blocks=0, rtextents=0
:Workin fine here! swidth/sunit = 14 used hdds which is useable space on the
raid6
[output with encryption]
mkfs.xfs -f /dev/mapper/raid6
meta-data=/dev/mapper/raid6 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
b7f57ad0: Badness in key lookup (length)
bp=(bno 13673620728, len 131072 bytes) key=(bno 13673620728, len 4096 bytes)
: not workin at all :/
[output with usin dev/md0 values]
mkfs.xfs -s size=4096 -d sunit=32,swidth=448 -r extsize=1835008
/dev/mapper/raid6
meta-data=/dev/mapper/raid6 isize=256 agcount=32, agsize=53412584
blks
= sectsz=4096 attr=0
data = bsize=4096 blocks=1709202592, imaxpct=25
= sunit=4 swidth=56 blks, unwritten=1
naming =version 2 bsize=4096
log =internal log bsize=4096 blocks=32768, version=2
= sectsz=4096 sunit=1 blks, lazy-count=0
realtime =none extsz=1835008 blocks=0, rtextents=0
b7f66ad0: Badness in key lookup (length)
bp=(bno 13673620728, len 131072 bytes) key=(bno 13673620728, len 4096 bytes)
:its still using wrong values here :/
[System Details]
mdadm --detail /dev/md0
/dev/md0:
Version : 00.90.03
Creation Time : Tue Sep 18 09:51:12 2007
Raid Level : raid6
Array Size : 6836811520 ( 6520.09 GiB 7000.89 GB)
Used Dev Size : 488343680 (465.72 GiB 500.06 GB)
Raid Devices : 16
Total Devices : 16
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Wed Sep 19 19:53:29 2007
State : clean
Active Devices : 16
Working Devices : 16
Failed Devices : 0
Spare Devices : 0
Chunk Size : 128K
UUID : ae1231f4:1b4dc7a0:370b3052:b437b3a1
Events : 0.18
Number Major Minor RaidDevice State
0 8 17 0 active sync /dev/sdb1
1 8 33 1 active sync /dev/sdc1
2 8 49 2 active sync /dev/sdd1
3 8 65 3 active sync /dev/sde1
4 8 81 4 active sync /dev/sdf1
5 8 97 5 active sync /dev/sdg1
6 8 113 6 active sync /dev/sdh1
7 8 129 7 active sync /dev/sdi1
8 8 145 8 active sync /dev/sdj1
9 8 161 9 active sync /dev/sdk1
10 8 177 10 active sync /dev/sdl1
11 8 193 11 active sync /dev/sdm1
12 8 209 12 active sync /dev/sdn1
13 8 225 13 active sync /dev/sdo1
14 8 241 14 active sync /dev/sdp1
15 65 1 15 active sync /dev/sdq1
cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md0 : active raid6 sdb1[0] sdq1[15] sdp1[14] sdo1[13] sdn1[12] sdm1[11]
sdl1[10] sdk1[9] sdj1[8] sdi1[7] sdh1[6] sdg1[5] sdf1[4] sde1[3] sdd1[2]
sdc1[1]
6836811520 blocks level 6, 128k chunk, algorithm 2 [16/16]
[UUUUUUUUUUUUUUUU]
------------------------------------------------
Best regards,
Jochen.
[[HTML alternate version deleted]]
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: Cant find sunit and swidth on luks encrypted raid6 device
2007-09-19 18:29 Cant find sunit and swidth on luks encrypted raid6 device Jochen K.
@ 2007-09-19 19:40 ` Bhagi rathi
2007-09-19 19:42 ` Eric Sandeen
1 sibling, 0 replies; 10+ messages in thread
From: Bhagi rathi @ 2007-09-19 19:40 UTC (permalink / raw)
To: Jochen K.; +Cc: xfs
Can we get strace output of mkfs.xfs -f /dev/mapper/raid6. It seems that we
are trying to access beyond the
end of the encrypted device. My guess is that we are reported with wrong
size from DKIOCGETBLOCKCOUNT
ioctl.
The easiest way to get configured is tell the size of the device by yourself
through
mkfs.dvfs -d size=<size_of_raid6> and all other parameters you want for sw,
su, etc.
This may work and give a try:)
-Cheers,
Bhagi.
On 9/19/07, Jochen K. <jochen.f.k@googlemail.com> wrote:
>
> Hi,
>
> I tried to create a xfs filesystem on a big encrypted mapped device but it
> isnt working at all.
> Also got latest kernel and kernel.org drivers for the raid controller.
> I hope you guys have any idea what might have happened here :)
> With ext3 its workin but i have no clue how to fix this problem.
>
>
> Kernel: 2.6.22.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686 i686 i386
> GNU/Linux
> mdadm - v2.6.3 - 20th August 2007
> cryptsetup 1.0.5
> mkfs.xfs version 2.9.4
>
> --added encryption--
> /sbin/cryptsetup -c aes-cbc-essiv:sha256 -y -s 256 luksFormat /dev/md0
> /sbin/cryptsetup luksOpen /dev/md0 raid6
>
> [output without encryption]
>
> mkfs.xfs /dev/md0
>
> meta-data=/dev/md0 isize=256 agcount=32, agsize=53412608
> blks
> = sectsz=4096 attr=0
> data = bsize=4096 blocks=1709202880,
> imaxpct=25
> = sunit=32 swidth=448 blks, unwritten=1
> naming =version 2 bsize=4096
> log =internal log bsize=4096 blocks=32768, version=2
> = sectsz=4096 sunit=1 blks, lazy-count=0
> realtime =none extsz=1835008 blocks=0, rtextents=0
>
> :Workin fine here! swidth/sunit = 14 used hdds which is useable space on
> the
> raid6
>
> [output with encryption]
>
> mkfs.xfs -f /dev/mapper/raid6
>
> meta-data=/dev/mapper/raid6 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
> b7f57ad0: Badness in key lookup (length)
> bp=(bno 13673620728, len 131072 bytes) key=(bno 13673620728, len 4096
> bytes)
>
> : not workin at all :/
>
> [output with usin dev/md0 values]
>
> mkfs.xfs -s size=4096 -d sunit=32,swidth=448 -r extsize=1835008
> /dev/mapper/raid6
>
> meta-data=/dev/mapper/raid6 isize=256 agcount=32, agsize=53412584
> blks
> = sectsz=4096 attr=0
> data = bsize=4096 blocks=1709202592,
> imaxpct=25
> = sunit=4 swidth=56 blks, unwritten=1
> naming =version 2 bsize=4096
> log =internal log bsize=4096 blocks=32768, version=2
> = sectsz=4096 sunit=1 blks, lazy-count=0
> realtime =none extsz=1835008 blocks=0, rtextents=0
> b7f66ad0: Badness in key lookup (length)
> bp=(bno 13673620728, len 131072 bytes) key=(bno 13673620728, len 4096
> bytes)
>
>
> :its still using wrong values here :/
>
> [System Details]
>
> mdadm --detail /dev/md0
> /dev/md0:
> Version : 00.90.03
> Creation Time : Tue Sep 18 09:51:12 2007
> Raid Level : raid6
> Array Size : 6836811520 ( 6520.09 GiB 7000.89 GB)
> Used Dev Size : 488343680 (465.72 GiB 500.06 GB)
> Raid Devices : 16
> Total Devices : 16
> Preferred Minor : 0
> Persistence : Superblock is persistent
>
> Update Time : Wed Sep 19 19:53:29 2007
> State : clean
> Active Devices : 16
> Working Devices : 16
> Failed Devices : 0
> Spare Devices : 0
>
> Chunk Size : 128K
>
> UUID : ae1231f4:1b4dc7a0:370b3052:b437b3a1
> Events : 0.18
>
> Number Major Minor RaidDevice State
> 0 8 17 0 active sync /dev/sdb1
> 1 8 33 1 active sync /dev/sdc1
> 2 8 49 2 active sync /dev/sdd1
> 3 8 65 3 active sync /dev/sde1
> 4 8 81 4 active sync /dev/sdf1
> 5 8 97 5 active sync /dev/sdg1
> 6 8 113 6 active sync /dev/sdh1
> 7 8 129 7 active sync /dev/sdi1
> 8 8 145 8 active sync /dev/sdj1
> 9 8 161 9 active sync /dev/sdk1
> 10 8 177 10 active sync /dev/sdl1
> 11 8 193 11 active sync /dev/sdm1
> 12 8 209 12 active sync /dev/sdn1
> 13 8 225 13 active sync /dev/sdo1
> 14 8 241 14 active sync /dev/sdp1
> 15 65 1 15 active sync /dev/sdq1
>
> cat /proc/mdstat
> Personalities : [raid6] [raid5] [raid4]
> md0 : active raid6 sdb1[0] sdq1[15] sdp1[14] sdo1[13] sdn1[12] sdm1[11]
> sdl1[10] sdk1[9] sdj1[8] sdi1[7] sdh1[6] sdg1[5] sdf1[4] sde1[3] sdd1[2]
> sdc1[1]
> 6836811520 blocks level 6, 128k chunk, algorithm 2 [16/16]
> [UUUUUUUUUUUUUUUU]
>
> ------------------------------------------------
>
>
> Best regards,
> Jochen.
>
>
> [[HTML alternate version deleted]]
>
>
>
[[HTML alternate version deleted]]
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Cant find sunit and swidth on luks encrypted raid6 device
2007-09-19 18:29 Cant find sunit and swidth on luks encrypted raid6 device Jochen K.
2007-09-19 19:40 ` Bhagi rathi
@ 2007-09-19 19:42 ` Eric Sandeen
2007-09-19 22:33 ` Eric Sandeen
` (2 more replies)
1 sibling, 3 replies; 10+ messages in thread
From: Eric Sandeen @ 2007-09-19 19:42 UTC (permalink / raw)
To: Jochen K.; +Cc: xfs
Jochen K. wrote:
> [output with encryption]
>
> mkfs.xfs -f /dev/mapper/raid6
>
> meta-data=/dev/mapper/raid6 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
> b7f57ad0: Badness in key lookup (length)
> bp=(bno 13673620728, len 131072 bytes) key=(bno 13673620728, len 4096 bytes)
What generates the last two lines in the above message, and do you know
what it indicates?
For one thing, I notice your filesystem comes out as different sizes,
1709202880 without encryption, 1709202592 with encryption (i.e.,
smaller) (these are 4k block units)
I assume the error message is trying to read or write 131072 bytes from
the offset 13673620728 * 512, or:
7000893812736 -> 7000893943807
The filesystem claims to end at:
1709202592 * 4096 = 7000893816832
which appears to be in the middle of the above range.
131072 is the amount that mkfs.xfs tries to zero at the end of a block
device. (you could confirm that it's this write by stracing mkfs,
perhaps?) It looks like somebody has the size wrong...
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?
-Eric
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: Cant find sunit and swidth on luks encrypted raid6 device
2007-09-19 19:42 ` Eric Sandeen
@ 2007-09-19 22:33 ` Eric Sandeen
2007-09-19 22:39 ` nscott
2007-09-20 0:54 ` Barry Naujok
2007-09-20 2:36 ` Barry Naujok
2 siblings, 1 reply; 10+ messages in thread
From: Eric Sandeen @ 2007-09-19 22:33 UTC (permalink / raw)
To: Eric Sandeen; +Cc: Jochen K., xfs
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
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: Cant find sunit and swidth on luks encrypted raid6 device
2007-09-19 22:33 ` Eric Sandeen
@ 2007-09-19 22:39 ` nscott
2007-09-19 22:47 ` Eric Sandeen
0 siblings, 1 reply; 10+ messages in thread
From: nscott @ 2007-09-19 22:39 UTC (permalink / raw)
To: Eric Sandeen; +Cc: Jochen K., xfs
> Eric Sandeen wrote:
>
> 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.
libxfs has been changing alot - most likely the problem lies in the buffer
caching
code there - Barry will probably recognise the error (when he gets online).
cheers.
--
Nathan
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Cant find sunit and swidth on luks encrypted raid6 device
2007-09-19 22:39 ` nscott
@ 2007-09-19 22:47 ` Eric Sandeen
2007-09-19 22:50 ` Jochen K.
0 siblings, 1 reply; 10+ messages in thread
From: Eric Sandeen @ 2007-09-19 22:47 UTC (permalink / raw)
To: nscott; +Cc: Jochen K., xfs
nscott@aconex.com wrote:
>> Eric Sandeen wrote:
>>
>> 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.
>
> libxfs has been changing alot - most likely the problem lies in the buffer
> caching
> code there - Barry will probably recognise the error (when he gets online).
--- xfs-cmds/xfsprogs/libxfs/rdwr.c 2007/02/21 14:37:52 1.34
+++ xfs-cmds/xfsprogs/libxfs/rdwr.c 2007/07/16 15:55:26 1.35
@@ -24,6 +24,8 @@
#define BDSTRAT_SIZE (256 * 1024)
#define min(x, y) ((x) < (y) ? (x) : (y))
+#define IO_BCOMPARE_CHECK
+
Yep.... :)
-Eric
> cheers.
>
> --
> Nathan
>
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Cant find sunit and swidth on luks encrypted raid6 device
2007-09-19 22:47 ` Eric Sandeen
@ 2007-09-19 22:50 ` Jochen K.
2007-09-19 22:56 ` Eric Sandeen
0 siblings, 1 reply; 10+ messages in thread
From: Jochen K. @ 2007-09-19 22:50 UTC (permalink / raw)
To: Eric Sandeen; +Cc: nscott, xfs
Hi, Eric
Here is the output you wanted. I also did some debuging with strace but its
kinda big to paste it in here.
I also tried with the size option using a smaller device size which was
working but still using wrong optimized values for the raid6 device.
I guess you found the bug up there so should I add that and recompile
xfsprogs to try again ?
mkfs.xfs -f -dsize=5t /dev/mapper/raid6
meta-data=/dev/mapper/raid6 isize=256 agcount=32, agsize=41943040
blks
= sectsz=512 attr=0
data = bsize=4096 blocks=1342177280, 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
Here is the output of blockdev and proc:
blockdev --getsize64 /dev/mapper/raid6
7000893943808
cat /proc/partitions
9 0 6836811520 md0
7 0 2150400 loop0
253 2 2149372 dm-2
253 3 6836810492 dm-3
-Jochen
[[HTML alternate version deleted]]
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: Cant find sunit and swidth on luks encrypted raid6 device
2007-09-19 22:50 ` Jochen K.
@ 2007-09-19 22:56 ` Eric Sandeen
0 siblings, 0 replies; 10+ messages in thread
From: Eric Sandeen @ 2007-09-19 22:56 UTC (permalink / raw)
To: Jochen K.; +Cc: nscott, xfs
Jochen K. wrote:
> Hi, Eric
>
> Here is the output you wanted. I also did some debuging with strace but
> its kinda big to paste it in here.
> I also tried with the size option using a smaller device size which was
> working but still using wrong optimized values for the raid6 device.
> I guess you found the bug up there so should I add that and recompile
> xfsprogs to try again ?
Let's let Barry chime in.
I got off on a luks thing, saw "key lookup" and thought it was unique to
luks. Didn't realize that message came from libxfs :) Oh well...
Also FWIW, the issue w/ sunit/swidth is unrelated to the error message.
It has more to do with xfs not knowing how to get that geometry out of
the encrypted block device (and hmmm is it even relevant in that case?
As long as it just encrypts each individual block, I suppose it still is
relevant).
-Eric
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Cant find sunit and swidth on luks encrypted raid6 device
2007-09-19 19:42 ` Eric Sandeen
2007-09-19 22:33 ` Eric Sandeen
@ 2007-09-20 0:54 ` Barry Naujok
2007-09-20 2:36 ` Barry Naujok
2 siblings, 0 replies; 10+ messages in thread
From: Barry Naujok @ 2007-09-20 0:54 UTC (permalink / raw)
To: Eric Sandeen, Jochen K.; +Cc: xfs
On Thu, 20 Sep 2007 05:42:54 +1000, Eric Sandeen <sandeen@sandeen.net>
wrote:
> Jochen K. wrote:
>
>> [output with encryption]
>>
>> mkfs.xfs -f /dev/mapper/raid6
>>
>> meta-data=/dev/mapper/raid6 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
>> b7f57ad0: Badness in key lookup (length)
>> bp=(bno 13673620728, len 131072 bytes) key=(bno 13673620728, len 4096
>> bytes)
>
> What generates the last two lines in the above message, and do you know
> what it indicates?
One problem I discovered with libxfs and repair in the prefetch is the
handling of I/O to a block offset, but with different I/O size.
libxfs cannot handle this, so I enabled IO_BCOMPARE_CHECK to detect
any I/Os that have the same offset but different length. This is a
bad thing for libxfs and it can lose data coherency.
I need to know what mkfs is doing at that offset. Probably the simplest
way is to enable IO_DEBUG, rebuild and observe all the I/Os to libxfs.
Since it's mkfs, there shouldn't be too many I/Os in total.
If you want to be clever, use XFS_BUF_TRACING with gdb, that will
pin-point the exact location :)
Regards,
Barry.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Cant find sunit and swidth on luks encrypted raid6 device
2007-09-19 19:42 ` Eric Sandeen
2007-09-19 22:33 ` Eric Sandeen
2007-09-20 0:54 ` Barry Naujok
@ 2007-09-20 2:36 ` Barry Naujok
2 siblings, 0 replies; 10+ messages in thread
From: Barry Naujok @ 2007-09-20 2:36 UTC (permalink / raw)
To: Eric Sandeen, Jochen K.; +Cc: xfs
On Thu, 20 Sep 2007 05:42:54 +1000, Eric Sandeen <sandeen@sandeen.net>
wrote:
> Jochen K. wrote:
>
>> [output with encryption]
>>
>> mkfs.xfs -f /dev/mapper/raid6
>>
>> meta-data=/dev/mapper/raid6 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
>> b7f57ad0: Badness in key lookup (length)
>> bp=(bno 13673620728, len 131072 bytes) key=(bno 13673620728, len 4096
>> bytes)
>
> What generates the last two lines in the above message, and do you know
> what it indicates?
The following patch should fix this problem:
--- a/xfsprogs/mkfs/xfs_mkfs.c 2007-09-20 12:31:33.000000000 +1000
+++ b/xfsprogs/mkfs/xfs_mkfs.c 2007-09-20 12:28:46.698533734 +1000
@@ -2115,6 +2115,7 @@
BTOBB(WHACK_SIZE));
bzero(XFS_BUF_PTR(buf), WHACK_SIZE);
libxfs_writebuf(buf, LIBXFS_EXIT_ON_FAILURE);
+ libxfs_purgebuf(buf);
}
/*
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2007-09-20 2:32 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-09-19 18:29 Cant find sunit and swidth on luks encrypted raid6 device Jochen K.
2007-09-19 19:40 ` Bhagi rathi
2007-09-19 19:42 ` Eric Sandeen
2007-09-19 22:33 ` Eric Sandeen
2007-09-19 22:39 ` nscott
2007-09-19 22:47 ` Eric Sandeen
2007-09-19 22:50 ` Jochen K.
2007-09-19 22:56 ` Eric Sandeen
2007-09-20 0:54 ` Barry Naujok
2007-09-20 2:36 ` Barry Naujok
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox