On Mon, 2005-01-24 at 12:24, Andrew Tridgell wrote:
> Andreas,
>
> I'm starting to think the bug I saw is hardware error. [...]
The patch in my prevous message (Mon, 24 Jan 2005 00:32:16 +0100) still
makes sense, if only for cleanliness: Without it, the i_extra_isize
field of reserved inodes is
On Mon, Jan 24, 2005 at 10:24:55PM +1100, Andrew Tridgell wrote:
> Andreas,
>
> I'm starting to think the bug I saw is hardware error. I just got this
> while trying to reproduce it tonight:
>
> Jan 24 02:43:32 dev4-003 kernel: qlogicfc0 : abort failed
> Jan 24 02:43:32 dev4-003 kernel:
Andreas,
I'm starting to think the bug I saw is hardware error. I just got this
while trying to reproduce it tonight:
Jan 24 02:43:32 dev4-003 kernel: qlogicfc0 : abort failed
Jan 24 02:43:32 dev4-003 kernel: qlogicfc0 : firmware status is 4000 4
Jan 24 02:43:32 dev4-003 kernel: scsi: Device
Andreas,
I'm starting to think the bug I saw is hardware error. I just got this
while trying to reproduce it tonight:
Jan 24 02:43:32 dev4-003 kernel: qlogicfc0 : abort failed
Jan 24 02:43:32 dev4-003 kernel: qlogicfc0 : firmware status is 4000 4
Jan 24 02:43:32 dev4-003 kernel: scsi: Device
On Mon, Jan 24, 2005 at 10:24:55PM +1100, Andrew Tridgell wrote:
Andreas,
I'm starting to think the bug I saw is hardware error. I just got this
while trying to reproduce it tonight:
Jan 24 02:43:32 dev4-003 kernel: qlogicfc0 : abort failed
Jan 24 02:43:32 dev4-003 kernel: qlogicfc0 :
On Mon, 2005-01-24 at 12:24, Andrew Tridgell wrote:
Andreas,
I'm starting to think the bug I saw is hardware error. [...]
The patch in my prevous message (Mon, 24 Jan 2005 00:32:16 +0100) still
makes sense, if only for cleanliness: Without it, the i_extra_isize
field of reserved inodes is
On Sunday 23 January 2005 23:58, Andreas Gruenbacher wrote:
> > Jan 23 06:54:38 dev4-003 kernel: journal_bmap: journal block not found at
> > offset 1036 on sdc1 Jan 23 06:54:38 dev4-003 kernel: Aborting journal on
> > device sdc1.
>
> Are you using data journaling on that filesystem? Does this
Hello,
On Sunday 23 January 2005 23:09, Andrew Tridgell wrote:
> Andreas,
>
> > Tridge, can you beat the code some more?
> >
> > Andrew has the five fixes in 2.6.11-rc1-mm2.
>
> It seemed to pass dbench runs OK, but then I started simultaneously
> running dbench and nbench on two different
Andreas,
> Tridge, can you beat the code some more?
>
> Andrew has the five fixes in 2.6.11-rc1-mm2.
It seemed to pass dbench runs OK, but then I started simultaneously
running dbench and nbench on two different disks (I have a new test
machine with more disks available). I am getting
Andreas,
> Tridge, can you beat the code some more?
> Andrew has the five fixes in 2.6.11-rc1-mm2.
sorry for the delay. I've started to test 2.6.11-rc1-mm2 tonight. No
problems so far.
Cheers, Tridge
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
Andreas,
Tridge, can you beat the code some more?
Andrew has the five fixes in 2.6.11-rc1-mm2.
sorry for the delay. I've started to test 2.6.11-rc1-mm2 tonight. No
problems so far.
Cheers, Tridge
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a
Andreas,
Tridge, can you beat the code some more?
Andrew has the five fixes in 2.6.11-rc1-mm2.
It seemed to pass dbench runs OK, but then I started simultaneously
running dbench and nbench on two different disks (I have a new test
machine with more disks available). I am getting failures
Hello,
On Sunday 23 January 2005 23:09, Andrew Tridgell wrote:
Andreas,
Tridge, can you beat the code some more?
Andrew has the five fixes in 2.6.11-rc1-mm2.
It seemed to pass dbench runs OK, but then I started simultaneously
running dbench and nbench on two different disks (I have
On Sunday 23 January 2005 23:58, Andreas Gruenbacher wrote:
Jan 23 06:54:38 dev4-003 kernel: journal_bmap: journal block not found at
offset 1036 on sdc1 Jan 23 06:54:38 dev4-003 kernel: Aborting journal on
device sdc1.
Are you using data journaling on that filesystem? Does this test pass
On Fri, 2005-01-21 at 23:58, Stephen C. Tweedie wrote:
> Hi Andreas,
>
> On Thu, 2005-01-20 at 02:01, Andreas Gruenbacher wrote:
>
> > here is a set of fixes for ext3 in-inode attributes:
>
> Obvious first question --- have these diffs survived the same
> torture-by-tridgell that the previous
Hi Andreas,
On Thu, 2005-01-20 at 02:01, Andreas Gruenbacher wrote:
> here is a set of fixes for ext3 in-inode attributes:
Obvious first question --- have these diffs survived the same
torture-by-tridgell that the previous batch suffered?
Cheers,
Stephen
-
To unsubscribe from this list: send
Hi Andreas,
On Thu, 2005-01-20 at 02:01, Andreas Gruenbacher wrote:
here is a set of fixes for ext3 in-inode attributes:
Obvious first question --- have these diffs survived the same
torture-by-tridgell that the previous batch suffered?
Cheers,
Stephen
-
To unsubscribe from this list: send
On Fri, 2005-01-21 at 23:58, Stephen C. Tweedie wrote:
Hi Andreas,
On Thu, 2005-01-20 at 02:01, Andreas Gruenbacher wrote:
here is a set of fixes for ext3 in-inode attributes:
Obvious first question --- have these diffs survived the same
torture-by-tridgell that the previous batch
Hello,
here is a set of fixes for ext3 in-inode attributes:
patches/ea-xattr-nolock.diff
No lock needed when freeing inode
The effect of the additional lock taking is very minor, but
it's still unnecessary.
patches/ea-xattr-update-sb.diff
Set the EXT3_FEATURE_COMPAT_EXT_ATTR for
Hello,
here is a set of fixes for ext3 in-inode attributes:
patches/ea-xattr-nolock.diff
No lock needed when freeing inode
The effect of the additional lock taking is very minor, but
it's still unnecessary.
patches/ea-xattr-update-sb.diff
Set the EXT3_FEATURE_COMPAT_EXT_ATTR for
20 matches
Mail list logo
