UP
Tigran Aivazian wrote:
>
> Mohammad,
>
> can you please tell me if that 4K corrupted block in a file was on a UP
> machine or SMP? So far I have not seen a corruption on UP machines, only
> SMP.
--
=
Mohammad A. Haque
Mohammad,
can you please tell me if that 4K corrupted block in a file was on a UP
machine or SMP? So far I have not seen a corruption on UP machines, only
SMP.
Regards,
Tigran
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
Mohammad,
can you please tell me if that 4K corrupted block in a file was on a UP
machine or SMP? So far I have not seen a corruption on UP machines, only
SMP.
Regards,
Tigran
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
UP
Tigran Aivazian wrote:
Mohammad,
can you please tell me if that 4K corrupted block in a file was on a UP
machine or SMP? So far I have not seen a corruption on UP machines, only
SMP.
--
=
Mohammad A. Haque
Whoops, my bad. Yes, 4k blocks.
Block size: 4096
Ion Badulescu wrote:
>
> No, you misunderstood me. df is always going to say 1k-blocks, but that
> doesn't mean that the filesystem's allocation unit is actually 1k.
>
> Try doing a tune2fs -l on the device holding the filesystem
On Wed, 29 Nov 2000, Mohammad A. Haque wrote:
> [mhaque@viper mhaque]$ df
> Filesystem 1k-blocks Used Available Use% Mounted on
> /dev/hda3 12737128 9988400 2101712 83% /
> /dev/hda246668 15106 29153 35% /boot
> /dev/hdd1
[mhaque@viper mhaque]$ df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/hda3 12737128 9988400 2101712 83% /
/dev/hda246668 15106 29153 35% /boot
/dev/hdd1 44327416 26319188 15756484 63% /home2
none
On Tue, 28 Nov 2000 23:37:49 -0500, Mohammad A. Haque <[EMAIL PROTECTED]> wrote:
> Ok, I just found a file with about the first 4k of it filled with nulls
> (^@^@). No telling if this was a result of what originally started this
> thread or not. I hadn't accessed that file since Nov 9th.
1k- or
Ok, I just found a file with about the first 4k of it filled with nulls
(^@^@). No telling if this was a result of what originally started this
thread or not. I hadn't accessed that file since Nov 9th.
--
=
Mohammad A. Haque
Ok, I'm not sure what else to try. I've even tried throwing around 1.6
GB of data, and copying and deleting at the same time. Nothing. Again,
this is _without_ the patches sent by Alexander.
I think I'm just gonna go on to test12-pre2.
Neil Brown wrote:
>
> Turns out my data is a false alarm.
Ok, I'm not sure what else to try. I've even tried throwing around 1.6
GB of data, and copying and deleting at the same time. Nothing. Again,
this is _without_ the patches sent by Alexander.
I think I'm just gonna go on to test12-pre2.
Neil Brown wrote:
Turns out my data is a false alarm.
Ok, I just found a file with about the first 4k of it filled with nulls
(^@^@). No telling if this was a result of what originally started this
thread or not. I hadn't accessed that file since Nov 9th.
--
=
Mohammad A. Haque
On Tue, 28 Nov 2000 23:37:49 -0500, Mohammad A. Haque [EMAIL PROTECTED] wrote:
Ok, I just found a file with about the first 4k of it filled with nulls
(^@^@). No telling if this was a result of what originally started this
thread or not. I hadn't accessed that file since Nov 9th.
1k- or
[mhaque@viper mhaque]$ df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/hda3 12737128 9988400 2101712 83% /
/dev/hda246668 15106 29153 35% /boot
/dev/hdd1 44327416 26319188 15756484 63% /home2
none
On Wed, 29 Nov 2000, Mohammad A. Haque wrote:
[mhaque@viper mhaque]$ df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/hda3 12737128 9988400 2101712 83% /
/dev/hda246668 15106 29153 35% /boot
/dev/hdd1 44327416
Whoops, my bad. Yes, 4k blocks.
Block size: 4096
Ion Badulescu wrote:
No, you misunderstood me. df is always going to say 1k-blocks, but that
doesn't mean that the filesystem's allocation unit is actually 1k.
Try doing a tune2fs -l on the device holding the filesystem and
On Friday November 24, [EMAIL PROTECTED] wrote:
>
>
> On Fri, 24 Nov 2000, Neil Brown wrote:
>
> > I ran my test script, which builds a variety of raid5 arrays with
> > varying numbers of drives and chunk sizes, and runs mkfs/bonnie/dbench
> > on each array, and it got through about 8 file
On Friday November 24, [EMAIL PROTECTED] wrote:
On Fri, 24 Nov 2000, Neil Brown wrote:
I ran my test script, which builds a variety of raid5 arrays with
varying numbers of drives and chunk sizes, and runs mkfs/bonnie/dbench
on each array, and it got through about 8 file systems but
I read up on this thread in the archives (the last message in thread was
posted on the 24th) so I'm sorry if this has already been said.
I'm having the same problem with 2.4.0-test10, but I don't have the
problem with 2.4.0-test9. So i think the bug might have been introduced
in 10.
When I try
I read up on this thread in the archives (the last message in thread was
posted on the 24th) so I'm sorry if this has already been said.
I'm having the same problem with 2.4.0-test10, but I don't have the
problem with 2.4.0-test9. So i think the bug might have been introduced
in 10.
When I try
On Fri, 24 Nov 2000, Mike Ricketts wrote:
> On Fri, 24 Nov 2000, Ion Badulescu wrote:
>
> > So I'm asking the same question, to all those who have seen unexplained
> > filesystem corruption with 2.4.0: are you using IDE drives? If the answer
> > is yes, can you check the logs and see if, at
In article <[EMAIL PROTECTED]>,
Guest section DW <[EMAIL PROTECTED]> wrote:
>
>(But I described the situation where the data on disk was correct
>and the date in core was not - almost certainly this is not an IDE problem.)
Ehh.. It only means that it would have been a read failure instead of a
I get the following followingon every reboot once.
Nov 23 01:14:37 viper kernel: hdb: drive_cmd: status=0x51 { DriveReady
SeekComplete Error }
Nov 23 01:14:37 viper kernel: hdb: drive_cmd: error=0x04
Nov 23 01:14:37 viper kernel: hdb: drive_cmd: status=0x51 { DriveReady
SeekComplete Error }
Nov
I have seen ext2 filesystem corruption both on SCSI and IDE drives.
Tigran
On Fri, 24 Nov 2000, Mike Ricketts wrote:
> On Fri, 24 Nov 2000, Ion Badulescu wrote:
>
> > So I'm asking the same question, to all those who have seen unexplained
> > filesystem corruption with 2.4.0: are you using
On Fri, 24 Nov 2000, Ion Badulescu wrote:
> So I'm asking the same question, to all those who have seen unexplained
> filesystem corruption with 2.4.0: are you using IDE drives? If the answer
> is yes, can you check the logs and see if, at *any* point before the
> corruption occurred, the IDE
On Fri, 24 Nov 2000, Mohammad A. Haque wrote:
> Yep. Unless of course they are SCSI with an identity crisis =P
Ok. Are there any IDE-related errors in your logs prior to getting the f/s
corruption? They could be relevant no matter how much time passed between
them and the first signs of
On Thu, 23 Nov 2000, Andre Hedrick wrote:
> Since there have been not kernel changes to the driver that effect the
> code since 2.4.0-test5 or test6 and it now randomly shows up after five or
> six revisions out from the change, and the changes were chipset only.
>
> Please make your point.
My
On Thu, 23 Nov 2000, Andre Hedrick wrote:
Since there have been not kernel changes to the driver that effect the
code since 2.4.0-test5 or test6 and it now randomly shows up after five or
six revisions out from the change, and the changes were chipset only.
Please make your point.
My
On Fri, 24 Nov 2000, Mohammad A. Haque wrote:
Yep. Unless of course they are SCSI with an identity crisis =P
Ok. Are there any IDE-related errors in your logs prior to getting the f/s
corruption? They could be relevant no matter how much time passed between
them and the first signs of
On Fri, 24 Nov 2000, Ion Badulescu wrote:
So I'm asking the same question, to all those who have seen unexplained
filesystem corruption with 2.4.0: are you using IDE drives? If the answer
is yes, can you check the logs and see if, at *any* point before the
corruption occurred, the IDE driver
I have seen ext2 filesystem corruption both on SCSI and IDE drives.
Tigran
On Fri, 24 Nov 2000, Mike Ricketts wrote:
On Fri, 24 Nov 2000, Ion Badulescu wrote:
So I'm asking the same question, to all those who have seen unexplained
filesystem corruption with 2.4.0: are you using IDE
I get the following followingon every reboot once.
Nov 23 01:14:37 viper kernel: hdb: drive_cmd: status=0x51 { DriveReady
SeekComplete Error }
Nov 23 01:14:37 viper kernel: hdb: drive_cmd: error=0x04
Nov 23 01:14:37 viper kernel: hdb: drive_cmd: status=0x51 { DriveReady
SeekComplete Error }
Nov
In article [EMAIL PROTECTED],
Guest section DW [EMAIL PROTECTED] wrote:
(But I described the situation where the data on disk was correct
and the date in core was not - almost certainly this is not an IDE problem.)
Ehh.. It only means that it would have been a read failure instead of a
write
On Fri, 24 Nov 2000, Mike Ricketts wrote:
On Fri, 24 Nov 2000, Ion Badulescu wrote:
So I'm asking the same question, to all those who have seen unexplained
filesystem corruption with 2.4.0: are you using IDE drives? If the answer
is yes, can you check the logs and see if, at *any* point
On Fri, 24 Nov 2000, Alexander Viro wrote:
> I don't see any attempts to tag you (or ATA subsystem, for that matter)
> in that thread. And thread is hardly bogus... I agree that changes in
We agree that the "thread" is valid, trust that point.
There was a quick pointed question that present,
On Thu, 23 Nov 2000, Andre Hedrick wrote:
[I wrote]
> > ?
> > If you have a l-k feed from future - please share. I'm not saying that
>
> Date: Thu, 23 Nov 2000 04:37:21 -0500 (EST)
>
> > fs/* is not the source of that stuff, but I sure as hell had not said
> > that it is. I simply don't know
On Fri, 24 Nov 2000, Alexander Viro wrote:
>
>
> On Thu, 23 Nov 2000, Andre Hedrick wrote:
>
> > What the F*** does that have to do with the price of eggs in china, heh?
> > Just maybe if you could follow a thread, you would see that that Alex Viro
> > has pointed out that changes in the FS
On Thu, 23 Nov 2000, Andre Hedrick wrote:
> What the F*** does that have to do with the price of eggs in china, heh?
> Just maybe if you could follow a thread, you would see that that Alex Viro
> has pointed out that changes in the FS layer as dorked things.
?
If you have a l-k feed from
On Thu, 23 Nov 2000, Ion Badulescu wrote:
> > Yesterday I had a diff -r showing that the old version
> > was corrupted and the new was OK. Of course a second
> > look showed that the old version also was OK, the corruption
> > must have been in the buffer cache, not on disk.)
>
> Are these
On Fri, 24 Nov 2000, Mohammad A. Haque wrote:
> I got the error while I was compiling XFree86 4 CVS and kernel. So
> that's what I've been doing in multiples along witha couple otehr things
> thrown inthe mix to generate lots of disk i/o.
Error messages would be interesting... So far we have
I got the error while I was compiling XFree86 4 CVS and kernel. So
that's what I've been doing in multiples along witha couple otehr things
thrown inthe mix to generate lots of disk i/o.
Nothing yet, but I'm pretty sure my machine hates me for putting it
through this.
Alexander Viro wrote:
>
Yep. Unless of course they are SCSI with an identity crisis =P
Ion Badulescu wrote:
>
> Are these disks IDE disks by any chance?
>
> Ion
>
--
=
Mohammad A. Haque http://www.haque.net/
On Fri, 24 Nov 2000, Neil Brown wrote:
> I ran my test script, which builds a variety of raid5 arrays with
> varying numbers of drives and chunk sizes, and runs mkfs/bonnie/dbench
> on each array, and it got through about 8 file systems but choked on
> the 9th by trying to allocate lots of
On Thu, Nov 23, 2000 at 08:58:39PM -0800, Ion Badulescu wrote:
> > (I am reorganizing my disks, copying large trees from
> > one place to the other. Always doing a diff -r between
> > old and new before removing the old version.
> > Yesterday I had a diff -r showing that the old version
> > was
On Thu, 23 Nov 2000 13:52:52 +0100, Guest section DW <[EMAIL PROTECTED]> wrote:
> On Thu, Nov 23, 2000 at 05:03:00PM +1100, Neil Brown wrote:
>
>> Oh, good. It's not just me and Tigran then.
>
> You have it all backwards. It would be good if it were
> just you and Tigran. Unfortunately it also
On Thursday November 23, [EMAIL PROTECTED] wrote:
>
>
> On Thu, 23 Nov 2000, Alexander Viro wrote:
>
> > On Thu, 23 Nov 2000, Neil Brown wrote:
> >
> > > which enabled ext2_notify_change, however ext2_notify_change has a
> > > bug.
> > > It sets attributes from iattr->ia_attr_flags even
> > >
I'm still trying to reproduce the darn thing w/o the patch. No luck so
far.
Maybe I'll put some mission critical stuff on my machine. Then it'll pop
up like clock works. Thats the way everythign is supposed to work right?
=)
Tigran Aivazian wrote:
> However, I can't say that _without_ your
Hi Alexander,
I am "hammering" an ext2 filesystem with all sorts (bonnies, make -j8
bzImage, cp -a dir1 dir2 + all these over localhost NFSv3) for a while and
so far it survives. The system is 2way SMP with 1G RAM.
However, I can't say that _without_ your patch the above did _not_
survive. The
On Thu, 23 Nov 2000, Alexander Viro wrote:
> On Thu, 23 Nov 2000, Neil Brown wrote:
>
> > which enabled ext2_notify_change, however ext2_notify_change has a
> > bug.
> > It sets attributes from iattr->ia_attr_flags even
> > if ATTR_ATTR_FLAG is NOT SET in iattr->ia_valid.
>
> Arrrgh. Could
On Thu, Nov 23, 2000 at 05:03:00PM +1100, Neil Brown wrote:
> Oh, good. It's not just me and Tigran then.
You have it all backwards. It would be good if it were
just you and Tigran. Unfortunately it also hits me.
(I am reorganizing my disks, copying large trees from
one place to the other.
On Thursday November 23, [EMAIL PROTECTED] wrote:
> On Thursday November 23, [EMAIL PROTECTED] wrote:
> >
> > Guys, could you try to reproduce it with the following:
>
> Well, I tried but it didn't go real well.
>
.
> It looks like extending a file is not allowed any more.
>
> This is
On Thursday November 23, [EMAIL PROTECTED] wrote:
>
> Guys, could you try to reproduce it with the following:
Well, I tried but it didn't go real well.
I build a 2 drive raid5 array (the script goes on to 3,4,5,6,7 drive
arrays), ran mkfs, mounted, ran "hdparm -t" on /dev/md0, ran bonnie.
On Thu, 23 Nov 2000, Neil Brown wrote:
> Oh, good. It's not just me and Tigran then. I was at first blaming
> my raid5 code for this, but if you get it and Tigran gets it (reported
> http://boudicca.tux.org/hypermail/linux-kernel/2000week48/0257.html
> ) then it's probably not me.
>
>
On Thu, 23 Nov 2000, Neil Brown wrote:
Oh, good. It's not just me and Tigran then. I was at first blaming
my raid5 code for this, but if you get it and Tigran gets it (reported
http://boudicca.tux.org/hypermail/linux-kernel/2000week48/0257.html
) then it's probably not me.
And
On Thursday November 23, [EMAIL PROTECTED] wrote:
Guys, could you try to reproduce it with the following:
Well, I tried but it didn't go real well.
I build a 2 drive raid5 array (the script goes on to 3,4,5,6,7 drive
arrays), ran mkfs, mounted, ran "hdparm -t" on /dev/md0, ran bonnie.
So
On Thursday November 23, [EMAIL PROTECTED] wrote:
On Thursday November 23, [EMAIL PROTECTED] wrote:
Guys, could you try to reproduce it with the following:
Well, I tried but it didn't go real well.
.
It looks like extending a file is not allowed any more.
This is with
On Thu, Nov 23, 2000 at 05:03:00PM +1100, Neil Brown wrote:
Oh, good. It's not just me and Tigran then.
You have it all backwards. It would be good if it were
just you and Tigran. Unfortunately it also hits me.
(I am reorganizing my disks, copying large trees from
one place to the other.
On Thu, 23 Nov 2000, Alexander Viro wrote:
On Thu, 23 Nov 2000, Neil Brown wrote:
which enabled ext2_notify_change, however ext2_notify_change has a
bug.
It sets attributes from iattr-ia_attr_flags even
if ATTR_ATTR_FLAG is NOT SET in iattr-ia_valid.
Arrrgh. Could you try that:
I'm still trying to reproduce the darn thing w/o the patch. No luck so
far.
Maybe I'll put some mission critical stuff on my machine. Then it'll pop
up like clock works. Thats the way everythign is supposed to work right?
=)
Tigran Aivazian wrote:
However, I can't say that _without_ your patch
Hi Alexander,
I am "hammering" an ext2 filesystem with all sorts (bonnies, make -j8
bzImage, cp -a dir1 dir2 + all these over localhost NFSv3) for a while and
so far it survives. The system is 2way SMP with 1G RAM.
However, I can't say that _without_ your patch the above did _not_
survive. The
On Thursday November 23, [EMAIL PROTECTED] wrote:
On Thu, 23 Nov 2000, Alexander Viro wrote:
On Thu, 23 Nov 2000, Neil Brown wrote:
which enabled ext2_notify_change, however ext2_notify_change has a
bug.
It sets attributes from iattr-ia_attr_flags even
if ATTR_ATTR_FLAG is
On Thu, 23 Nov 2000 13:52:52 +0100, Guest section DW [EMAIL PROTECTED] wrote:
On Thu, Nov 23, 2000 at 05:03:00PM +1100, Neil Brown wrote:
Oh, good. It's not just me and Tigran then.
You have it all backwards. It would be good if it were
just you and Tigran. Unfortunately it also hits me.
On Thu, Nov 23, 2000 at 08:58:39PM -0800, Ion Badulescu wrote:
(I am reorganizing my disks, copying large trees from
one place to the other. Always doing a diff -r between
old and new before removing the old version.
Yesterday I had a diff -r showing that the old version
was corrupted
On Fri, 24 Nov 2000, Neil Brown wrote:
I ran my test script, which builds a variety of raid5 arrays with
varying numbers of drives and chunk sizes, and runs mkfs/bonnie/dbench
on each array, and it got through about 8 file systems but choked on
the 9th by trying to allocate lots of blocks
Yep. Unless of course they are SCSI with an identity crisis =P
Ion Badulescu wrote:
Are these disks IDE disks by any chance?
Ion
--
=
Mohammad A. Haque http://www.haque.net/
I got the error while I was compiling XFree86 4 CVS and kernel. So
that's what I've been doing in multiples along witha couple otehr things
thrown inthe mix to generate lots of disk i/o.
Nothing yet, but I'm pretty sure my machine hates me for putting it
through this.
Alexander Viro wrote:
On Fri, 24 Nov 2000, Mohammad A. Haque wrote:
I got the error while I was compiling XFree86 4 CVS and kernel. So
that's what I've been doing in multiples along witha couple otehr things
thrown inthe mix to generate lots of disk i/o.
Error messages would be interesting... So far we have
On Thu, 23 Nov 2000, Ion Badulescu wrote:
Yesterday I had a diff -r showing that the old version
was corrupted and the new was OK. Of course a second
look showed that the old version also was OK, the corruption
must have been in the buffer cache, not on disk.)
Are these disks IDE
On Thu, 23 Nov 2000, Andre Hedrick wrote:
What the F*** does that have to do with the price of eggs in china, heh?
Just maybe if you could follow a thread, you would see that that Alex Viro
has pointed out that changes in the FS layer as dorked things.
?
If you have a l-k feed from future
On Fri, 24 Nov 2000, Alexander Viro wrote:
On Thu, 23 Nov 2000, Andre Hedrick wrote:
What the F*** does that have to do with the price of eggs in china, heh?
Just maybe if you could follow a thread, you would see that that Alex Viro
has pointed out that changes in the FS layer as
On Thu, 23 Nov 2000, Andre Hedrick wrote:
[I wrote]
?
If you have a l-k feed from future - please share. I'm not saying that
Date: Thu, 23 Nov 2000 04:37:21 -0500 (EST)
fs/* is not the source of that stuff, but I sure as hell had not said
that it is. I simply don't know yet.
On Fri, 24 Nov 2000, Alexander Viro wrote:
shrug I don't see any attempts to tag you (or ATA subsystem, for that matter)
in that thread. And thread is hardly bogus... I agree that changes in
We agree that the "thread" is valid, trust that point.
There was a quick pointed question that
> 540028982 = 0x20303036 = " 336"
> 540024880 = 0x20302030 = " 3 3"
> 170926128 = 0x0a302030 = "\n3 3"
>
These should be:
540028982 = 0x20303036 = " 006"
540024880 = 0x20302030 = " 0 0"
170926128 = 0x0a302030 = "\n0 0"
/Pär-Ola Nilsson
-
To unsubscribe from this list: send the line
Mohammad A. Haque writes:
> I just got these while doing many compiles on my box
>
> Nov 23 00:40:06 viper kernel: EXT2-fs warning (device ide0(3,3)):
> ext2_unlink: Deleting nonexistent file (622295), 0
> Nov 23 00:40:06 viper kernel: = 1
> Nov 23 00:40:06 viper kernel: EXT2-fs error
On Thursday November 23, [EMAIL PROTECTED] wrote:
> I just got these while doing many compiles on my box
>
> Nov 23 00:40:06 viper kernel: EXT2-fs warning (device ide0(3,3)):
> ext2_unlink: Deleting nonexistent file (622295), 0
> Nov 23 00:40:06 viper kernel: = 1
> Nov 23 00:40:06 viper
I just got these while doing many compiles on my box
Nov 23 00:40:06 viper kernel: EXT2-fs warning (device ide0(3,3)):
ext2_unlink: Deleting nonexistent file (622295), 0
Nov 23 00:40:06 viper kernel: = 1
Nov 23 00:40:06 viper kernel: EXT2-fs error (device ide0(3,3)):
ext2_free_blocks:
I just got these while doing many compiles on my box
Nov 23 00:40:06 viper kernel: EXT2-fs warning (device ide0(3,3)):
ext2_unlink: Deleting nonexistent file (622295), 0
Nov 23 00:40:06 viper kernel: = 1
Nov 23 00:40:06 viper kernel: EXT2-fs error (device ide0(3,3)):
ext2_free_blocks:
On Thursday November 23, [EMAIL PROTECTED] wrote:
I just got these while doing many compiles on my box
Nov 23 00:40:06 viper kernel: EXT2-fs warning (device ide0(3,3)):
ext2_unlink: Deleting nonexistent file (622295), 0
Nov 23 00:40:06 viper kernel: = 1
Nov 23 00:40:06 viper kernel:
Mohammad A. Haque writes:
I just got these while doing many compiles on my box
Nov 23 00:40:06 viper kernel: EXT2-fs warning (device ide0(3,3)):
ext2_unlink: Deleting nonexistent file (622295), 0
Nov 23 00:40:06 viper kernel: = 1
Nov 23 00:40:06 viper kernel: EXT2-fs error (device
540028982 = 0x20303036 = " 336"
540024880 = 0x20302030 = " 3 3"
170926128 = 0x0a302030 = "\n3 3"
These should be:
540028982 = 0x20303036 = " 006"
540024880 = 0x20302030 = " 0 0"
170926128 = 0x0a302030 = "\n0 0"
/Pär-Ola Nilsson
-
To unsubscribe from this list: send the line "unsubscribe
80 matches
Mail list logo
