It sounds like a possible HW issue. Could also be your partition setup
too. You don't have overlapping partitions do you? Just curious.
In regards to 2.4.17, I'm running it on my 1550 at my desk, but I have
problems with that kernel corrupting files from time to time. I'm not
sure what the deal is but 2.4.14 was the last kernel I could run without
ANY problems what so ever. I'm hoping 2.4.18 will be better.
On Mon, 2002-01-21 at 13:11, Daniel Just wrote:
> Hello list,
>
> today I wanted to try what happens if I create a file bigger than 2GB
> on my debian woody box with 2.4.17-xfs (xfs-2.4.17-all-i386.bz2,
> should be of 01/10/01, also with preempt-patch 2.4.17-1, compiled with
> gcc 2.95.4). So I tried as a "normal user"
>
> $ dd if=/dev/zero of=bigone bs=1M count=3000
>
> Some time later, dd apparently got stuck at 1.4G, I pressed CTRL-C and
> it stopped. Having a look at /var/log/messages I found tons of these:
>
> Jan 21 14:55:42 maryland kernel: xfs_alloc_read_agf: error in
> <ide1(22,3)> AG 0
> Jan 21 14:55:42
maryland kernel: bad agf_magicnum 0x0
> Jan 21 14:55:42 maryland kernel: Bad version number 0x0
>
> After umounting that partition, I ran xfs_check and xfs_repair
> which brought some messages I unfortunately didn't keep.
> Afterwards I had some stuff in lost+found, also some files got lost.
> (But I had a backup handy, so... :->)
>
> What happened here? XFS-Problem? Hardware-Problem? Compiler-Issue?
> User-Failure? Please ask, if you need more information.
>
> Best regards and thanks in advance,
>
> Daniel
--
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-698-7250
email: austin@xxxxxxxxxxxxxxx
"It is the part of a good shepherd to shear his flock, not to skin it."
Latin Proverb
signature.asc
Description: This is a digitally signed message part
|