* Problem with fsstress on powerpc
@ 2008-04-08 15:24 Aneesh Kumar K.V
2008-04-09 7:44 ` Dmitri Monakhov
0 siblings, 1 reply; 6+ messages in thread
From: Aneesh Kumar K.V @ 2008-04-08 15:24 UTC (permalink / raw)
To: Eric Sandeen, Mingming Cao; +Cc: ext4 development
Hi All,
Test case: fsstress with fallocate test case added.
Inode 8170, i_size is 0, should be 839680. Fix? no
tst_extents: stat <8170>
header: magic=af3 entries=512 max=1024 depth=0 generation=0
(Left 1)
(Left 0)
Inode: 8170 Type: regular Mode: 0666 Flags: 0x80000
Generation: 3214836894
User: 0 Group: 0 Size: 0
File ACL: 0 Directory ACL: 0
Links: 1 Blockcount: 96
Fragment: Address: 0 Number: 0 Size: 0
ctime: 0x47fb705f -- Tue Apr 8 09:17:19 2008
atime: 0x47fb6d1b -- Tue Apr 8 09:03:23 2008
mtime: 0x47fb705f -- Tue Apr 8 09:17:19 2008
Size of extra inode fields: 28
BLOCKS:
(193-198):1275331-1275336, (199-204):747341-747346
TOTAL: 12
tst_extents: inode <8170>
header: magic=af3 entries=512 max=1024 depth=0 generation=0
Loaded inode 8170
tst_extents: root
(Left 1)
extent: lblk 193--198, len 6, pblk 1275331, flags: LEAF
tst_extents: nl
(Left 0)
extent: lblk 199--204, len 6, pblk 747341, flags: LEAF
tst_extents: nl
nl: No 'next' extent
tst_extents:
[root@gekko-lp2 tmp]# ls -ali fsstress/p1b8/d0/da/d26/fc5
8170 -rw-rw-rw- 1 root root 0 Apr 8 09:17 fsstress/p1b8/d0/da/d26/fc5
Inode 179868, i_size is 724992, should be 868352. Fix? no
tst_extents: stat <179868>
header: magic=af3 entries=512 max=1024 depth=0 generation=0
(Left 1)
(Left 0)
Inode: 179868 Type: regular Mode: 0666 Flags: 0x80000
Generation: 3214716167
User: 122091 Group: 0 Size: 724992
File ACL: 0 Directory ACL: 0
Links: 1 Blockcount: 32
Fragment: Address: 0 Number: 0 Size: 0
ctime: 0x47fb7009 -- Tue Apr 8 09:15:53 2008
atime: 0x47fb6cd8 -- Tue Apr 8 09:02:16 2008
mtime: 0x47fb6f74 -- Tue Apr 8 09:13:24 2008
Size of extra inode fields: 28
BLOCKS:
(176):746755, (209-211):945533-945535
TOTAL: 4
tst_extents: inode <179868>
header: magic=af3 entries=512 max=1024 depth=0 generation=0
Loaded inode 179868
tst_extents: root
(Left 1)
extent: lblk 176--176, len 1, pblk 746755, flags: LEAF
tst_extents: nl
(Left 0)
extent: lblk 209--211, len 3, pblk 945533, flags: LEAF
tst_extents: nl
nl: No 'next' extent
tst_extents:
[root@gekko-lp2 tmp]# ls -alhi fsstress/p98/d3/d12/d1b/d20/d11e/df1/f5b
179868 -rw-rw-rw- 1 122091 root 708K Apr 8 09:13
fsstress/p98/d3/d12/d1b/d20/d11e/df1/f5b
The file system is 100% full
/dev/sda7 9.2G 9.2G 0 100% /mnt/tmp
-aneesh
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Problem with fsstress on powerpc
2008-04-08 15:24 Problem with fsstress on powerpc Aneesh Kumar K.V
@ 2008-04-09 7:44 ` Dmitri Monakhov
2008-04-09 8:21 ` Aneesh Kumar K.V
0 siblings, 1 reply; 6+ messages in thread
From: Dmitri Monakhov @ 2008-04-09 7:44 UTC (permalink / raw)
To: Aneesh Kumar K.V; +Cc: Eric Sandeen, Mingming Cao, ext4 development
On 20:54 Tue 08 Apr , Aneesh Kumar K.V wrote:
> Hi All,
>
> Test case: fsstress with fallocate test case added.
This may happens because of direct write.
Please add exact fsstess command and options.
>
> Inode 8170, i_size is 0, should be 839680. Fix? no
>
> tst_extents: stat <8170>
> header: magic=af3 entries=512 max=1024 depth=0 generation=0
> (Left 1)
> (Left 0)
> Inode: 8170 Type: regular Mode: 0666 Flags: 0x80000
> Generation: 3214836894
> User: 0 Group: 0 Size: 0
> File ACL: 0 Directory ACL: 0
> Links: 1 Blockcount: 96
> Fragment: Address: 0 Number: 0 Size: 0
> ctime: 0x47fb705f -- Tue Apr 8 09:17:19 2008
> atime: 0x47fb6d1b -- Tue Apr 8 09:03:23 2008
> mtime: 0x47fb705f -- Tue Apr 8 09:17:19 2008
> Size of extra inode fields: 28
> BLOCKS:
> (193-198):1275331-1275336, (199-204):747341-747346
> TOTAL: 12
>
> tst_extents: inode <8170>
> header: magic=af3 entries=512 max=1024 depth=0 generation=0
> Loaded inode 8170
> tst_extents: root
> (Left 1)
> extent: lblk 193--198, len 6, pblk 1275331, flags: LEAF
> tst_extents: nl
> (Left 0)
> extent: lblk 199--204, len 6, pblk 747341, flags: LEAF
> tst_extents: nl
> nl: No 'next' extent
> tst_extents:
>
> [root@gekko-lp2 tmp]# ls -ali fsstress/p1b8/d0/da/d26/fc5
> 8170 -rw-rw-rw- 1 root root 0 Apr 8 09:17 fsstress/p1b8/d0/da/d26/fc5
>
>
> Inode 179868, i_size is 724992, should be 868352. Fix? no
>
> tst_extents: stat <179868>
> header: magic=af3 entries=512 max=1024 depth=0 generation=0
> (Left 1)
> (Left 0)
> Inode: 179868 Type: regular Mode: 0666 Flags: 0x80000
> Generation: 3214716167
> User: 122091 Group: 0 Size: 724992
> File ACL: 0 Directory ACL: 0
> Links: 1 Blockcount: 32
> Fragment: Address: 0 Number: 0 Size: 0
> ctime: 0x47fb7009 -- Tue Apr 8 09:15:53 2008
> atime: 0x47fb6cd8 -- Tue Apr 8 09:02:16 2008
> mtime: 0x47fb6f74 -- Tue Apr 8 09:13:24 2008
> Size of extra inode fields: 28
> BLOCKS:
> (176):746755, (209-211):945533-945535
> TOTAL: 4
>
> tst_extents: inode <179868>
> header: magic=af3 entries=512 max=1024 depth=0 generation=0
> Loaded inode 179868
> tst_extents: root
> (Left 1)
> extent: lblk 176--176, len 1, pblk 746755, flags: LEAF
> tst_extents: nl
> (Left 0)
> extent: lblk 209--211, len 3, pblk 945533, flags: LEAF
> tst_extents: nl
> nl: No 'next' extent
> tst_extents:
>
> [root@gekko-lp2 tmp]# ls -alhi fsstress/p98/d3/d12/d1b/d20/d11e/df1/f5b
> 179868 -rw-rw-rw- 1 122091 root 708K Apr 8 09:13
> fsstress/p98/d3/d12/d1b/d20/d11e/df1/f5b
>
> The file system is 100% full
> /dev/sda7 9.2G 9.2G 0 100% /mnt/tmp
>
>
> -aneesh
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Problem with fsstress on powerpc
2008-04-09 7:44 ` Dmitri Monakhov
@ 2008-04-09 8:21 ` Aneesh Kumar K.V
2008-04-09 8:33 ` Dmitri Monakhov
0 siblings, 1 reply; 6+ messages in thread
From: Aneesh Kumar K.V @ 2008-04-09 8:21 UTC (permalink / raw)
To: Dmitri Monakhov; +Cc: Eric Sandeen, Mingming Cao, ext4 development
On Wed, Apr 09, 2008 at 11:44:57AM +0400, Dmitri Monakhov wrote:
> On 20:54 Tue 08 Apr , Aneesh Kumar K.V wrote:
> > Hi All,
> >
> > Test case: fsstress with fallocate test case added.
> This may happens because of direct write.
> Please add exact fsstess command and options.
> >
fsstress -c -n1000 -p1000 -d /mnt/tmp/
What i found was also related. The file which had errors had the below
operations on them.
82/901: dread d16/d20/d22/d2d/d63/d68/d9a/f93 [622592,53248] 0
82/939: dwrite d16/d20/d22/d2d/d63/d68/d9a/f93 [1093632,77824] 28
9/863: fallocate d1/d2d/d32/d8f/d97/d108/d9b/ffb [2041,75851] 28
18/733: fallocate d9/ddd/f86 [481025,18486] 0
18/735: dwrite d9/ddd/f86 [679936,36864] 0
18/764: dread d9/ddd/f86 [53248,8192] 0
18/910: dwrite d9/ddd/f86 [1454080,4096] 28
18/999: dwrite d9/ddd/f86 [1798144,61440] 28
But what would happen during direct write that cause this ?
-aneesh
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Problem with fsstress on powerpc
2008-04-09 8:21 ` Aneesh Kumar K.V
@ 2008-04-09 8:33 ` Dmitri Monakhov
2008-04-09 9:39 ` Aneesh Kumar K.V
0 siblings, 1 reply; 6+ messages in thread
From: Dmitri Monakhov @ 2008-04-09 8:33 UTC (permalink / raw)
To: Aneesh Kumar K.V; +Cc: Eric Sandeen, Mingming Cao, ext4 development
On 13:51 Wed 09 Apr , Aneesh Kumar K.V wrote:
> On Wed, Apr 09, 2008 at 11:44:57AM +0400, Dmitri Monakhov wrote:
> > On 20:54 Tue 08 Apr , Aneesh Kumar K.V wrote:
> > > Hi All,
> > >
> > > Test case: fsstress with fallocate test case added.
> > This may happens because of direct write.
> > Please add exact fsstess command and options.
> > >
>
> fsstress -c -n1000 -p1000 -d /mnt/tmp/
>
> What i found was also related. The file which had errors had the below
> operations on them.
>
> 82/901: dread d16/d20/d22/d2d/d63/d68/d9a/f93 [622592,53248] 0
> 82/939: dwrite d16/d20/d22/d2d/d63/d68/d9a/f93 [1093632,77824] 28
>
>
> 9/863: fallocate d1/d2d/d32/d8f/d97/d108/d9b/ffb [2041,75851] 28
>
>
> 18/733: fallocate d9/ddd/f86 [481025,18486] 0
> 18/735: dwrite d9/ddd/f86 [679936,36864] 0
> 18/764: dread d9/ddd/f86 [53248,8192] 0
> 18/910: dwrite d9/ddd/f86 [1454080,4096] 28
> 18/999: dwrite d9/ddd/f86 [1798144,61440] 28
>
>
> But what would happen during direct write that cause this ?
Ohh it is long live bug in direct-io error handling logic:
http://lkml.org/lkml/2006/12/18/103
So IMHO it is beter to disable direct-io writes in your case.
>
> -aneesh
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Problem with fsstress on powerpc
2008-04-09 8:33 ` Dmitri Monakhov
@ 2008-04-09 9:39 ` Aneesh Kumar K.V
2008-04-09 10:01 ` Dmitri Monakhov
0 siblings, 1 reply; 6+ messages in thread
From: Aneesh Kumar K.V @ 2008-04-09 9:39 UTC (permalink / raw)
To: Dmitri Monakhov; +Cc: Eric Sandeen, Mingming Cao, ext4 development
On Wed, Apr 09, 2008 at 12:33:41PM +0400, Dmitri Monakhov wrote:
> On 13:51 Wed 09 Apr , Aneesh Kumar K.V wrote:
> > On Wed, Apr 09, 2008 at 11:44:57AM +0400, Dmitri Monakhov wrote:
> > > On 20:54 Tue 08 Apr , Aneesh Kumar K.V wrote:
> > > > Hi All,
> > > >
> > > > Test case: fsstress with fallocate test case added.
> > > This may happens because of direct write.
> > > Please add exact fsstess command and options.
> > > >
> >
> > fsstress -c -n1000 -p1000 -d /mnt/tmp/
> >
> > What i found was also related. The file which had errors had the below
> > operations on them.
> >
> > 82/901: dread d16/d20/d22/d2d/d63/d68/d9a/f93 [622592,53248] 0
> > 82/939: dwrite d16/d20/d22/d2d/d63/d68/d9a/f93 [1093632,77824] 28
> >
> >
> > 9/863: fallocate d1/d2d/d32/d8f/d97/d108/d9b/ffb [2041,75851] 28
> >
> >
> > 18/733: fallocate d9/ddd/f86 [481025,18486] 0
> > 18/735: dwrite d9/ddd/f86 [679936,36864] 0
> > 18/764: dread d9/ddd/f86 [53248,8192] 0
> > 18/910: dwrite d9/ddd/f86 [1454080,4096] 28
> > 18/999: dwrite d9/ddd/f86 [1798144,61440] 28
> >
> >
> > But what would happen during direct write that cause this ?
> Ohh it is long live bug in direct-io error handling logic:
> http://lkml.org/lkml/2006/12/18/103
> So IMHO it is beter to disable direct-io writes in your case.
Why is the patch not yet available in the Linus tree ? Does this mean
that i will not be able to test direct io write at all. Right
now i did
#ifdef ENOSPC_BUG_DIRECT_IO_YES
{ OP_DREAD, "dread", dread_f, 4, 0 },
{ OP_DWRITE, "dwrite", dwrite_f, 4, 1 },
#endif
i am not interested in dread, so commented that also.
fsstress ran successfully with this change.
-aneesh
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: Problem with fsstress on powerpc
2008-04-09 9:39 ` Aneesh Kumar K.V
@ 2008-04-09 10:01 ` Dmitri Monakhov
0 siblings, 0 replies; 6+ messages in thread
From: Dmitri Monakhov @ 2008-04-09 10:01 UTC (permalink / raw)
To: Aneesh Kumar K.V; +Cc: Eric Sandeen, Mingming Cao, ext4 development
On 15:09 Wed 09 Apr , Aneesh Kumar K.V wrote:
> On Wed, Apr 09, 2008 at 12:33:41PM +0400, Dmitri Monakhov wrote:
> > On 13:51 Wed 09 Apr , Aneesh Kumar K.V wrote:
> > > On Wed, Apr 09, 2008 at 11:44:57AM +0400, Dmitri Monakhov wrote:
> > > > On 20:54 Tue 08 Apr , Aneesh Kumar K.V wrote:
> > > > > Hi All,
> > > > >
> > > > > Test case: fsstress with fallocate test case added.
> > > > This may happens because of direct write.
> > > > Please add exact fsstess command and options.
> > > > >
> > >
> > > fsstress -c -n1000 -p1000 -d /mnt/tmp/
> > >
> > > What i found was also related. The file which had errors had the below
> > > operations on them.
> > >
> > > 82/901: dread d16/d20/d22/d2d/d63/d68/d9a/f93 [622592,53248] 0
> > > 82/939: dwrite d16/d20/d22/d2d/d63/d68/d9a/f93 [1093632,77824] 28
> > >
> > >
> > > 9/863: fallocate d1/d2d/d32/d8f/d97/d108/d9b/ffb [2041,75851] 28
> > >
> > >
> > > 18/733: fallocate d9/ddd/f86 [481025,18486] 0
> > > 18/735: dwrite d9/ddd/f86 [679936,36864] 0
> > > 18/764: dread d9/ddd/f86 [53248,8192] 0
> > > 18/910: dwrite d9/ddd/f86 [1454080,4096] 28
> > > 18/999: dwrite d9/ddd/f86 [1798144,61440] 28
> > >
> > >
> > > But what would happen during direct write that cause this ?
> > Ohh it is long live bug in direct-io error handling logic:
> > http://lkml.org/lkml/2006/12/18/103
> > So IMHO it is beter to disable direct-io writes in your case.
>
> Why is the patch not yet available in the Linus tree ?
Because not everybody was happy about this solution. I'll send new version
today.
>Does this mean that i will not be able to test direct io write at all.
Strictly saying YES, but practically you can use direct-io writes if
you have enough disk space.
>Right now i did
>
> #ifdef ENOSPC_BUG_DIRECT_IO_YES
> { OP_DREAD, "dread", dread_f, 4, 0 },
> { OP_DWRITE, "dwrite", dwrite_f, 4, 1 },
> #endif
>
> i am not interested in dread, so commented that also.
>
> fsstress ran successfully with this change.
>
> -aneesh
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2008-04-09 10:09 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-04-08 15:24 Problem with fsstress on powerpc Aneesh Kumar K.V
2008-04-09 7:44 ` Dmitri Monakhov
2008-04-09 8:21 ` Aneesh Kumar K.V
2008-04-09 8:33 ` Dmitri Monakhov
2008-04-09 9:39 ` Aneesh Kumar K.V
2008-04-09 10:01 ` Dmitri Monakhov
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox