Hi,
David Chinner wrote:
On Tue, Mar 27, 2007 at 06:16:04PM +0200, Oliver Joa wrote:
Hi,
since some weeks i try to get my new hardware running:
Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz
Intel DP965LT Mainboard
Seagate SATA-Harddisk in AHCI-Mode
After some hours of running or after
Hi,
David Chinner wrote:
On Tue, Mar 27, 2007 at 06:16:04PM +0200, Oliver Joa wrote:
Hi,
since some weeks i try to get my new hardware running:
Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz
Intel DP965LT Mainboard
Seagate SATA-Harddisk in AHCI-Mode
After some hours of running or after
Hi,
David Chinner wrote:
[...]
Next time you get a shutdown, can you unmount the filesystems and
run xfs_check and then "xfs_repair -n" on the filesystem. These will
tell you the inode numbers that are bad. Can you post the errors
reported by these tools?
xfs_check gives this:
bad format
Hi,
David Chinner wrote:
[...]
Next time you get a shutdown, can you unmount the filesystems and
run xfs_check and then xfs_repair -n on the filesystem. These will
tell you the inode numbers that are bad. Can you post the errors
reported by these tools?
xfs_check gives this:
bad format 0
On Thu, Mar 29 2007, Jan Kara wrote:
> > Oliver Joa wrote:
> > >>eason or another, xfs has detected a corrupted on-disk inode format
> > >>which it cannot recognize, and shuts down.
> >
> > Oh, one other thing that may not apply in your case, but may.
> > Does your SATA disk support write
> Oliver Joa wrote:
> >>eason or another, xfs has detected a corrupted on-disk inode format
> >>which it cannot recognize, and shuts down.
>
> Oh, one other thing that may not apply in your case, but may.
> Does your SATA disk support write caching? Does it support
> something called a
Oliver Joa wrote:
eason or another, xfs has detected a corrupted on-disk inode format
which it cannot recognize, and shuts down.
Oh, one other thing that may not apply in your case, but may.
Does your SATA disk support write caching? Does it support
something called a barrier
On Thu, Mar 29 2007, Jan Kara wrote:
Oliver Joa wrote:
eason or another, xfs has detected a corrupted on-disk inode format
which it cannot recognize, and shuts down.
Oh, one other thing that may not apply in your case, but may.
Does your SATA disk support write caching? Does it
Oliver Joa wrote:
eason or another, xfs has detected a corrupted on-disk inode format
which it cannot recognize, and shuts down.
Oh, one other thing that may not apply in your case, but may.
Does your SATA disk support write caching? Does it support
something called a barrier function?
Oliver Joa wrote:
eason or another, xfs has detected a corrupted on-disk inode format
which it cannot recognize, and shuts down. It is likely the result
of something which has gone wrong previously. xfs_repair should fix
it. Are there other non-xfs messages in your logs indicating other
On Wed, Mar 28, 2007 at 02:42:00PM +0200, Oliver Joa wrote:
> Hi,
>
> David Chinner wrote:
>
> [...]
>
> >What is the corruption message in the log from XFS?
> >Can you please post that? Without it we really can't help you.
> >
> >Also, please check to see if there are any I/O errors
> >in the
Hi,
Eric Sandeen wrote:
[...]
For one reason or another, xfs has detected a corrupted on-disk inode
format which it cannot recognize, and shuts down. It is likely the
result of something which has gone wrong previously. xfs_repair should
fix it. Are there other non-xfs messages in your
Oliver Joa wrote:
Ok, here is a test:
test:/# find / -xdev | cpio -padm /test/
cpio: /usr/src/linux-2.6.20.2/Documentation/networking/NAPI_HOWTO.txt:
Structure needs cleaning
3648371 blocks
test:/#
That, cryptically enough, means that the filesystem has detected a
problem and has shut
Hi,
David Chinner wrote:
[...]
What is the corruption message in the log from XFS?
Can you please post that? Without it we really can't help you.
Also, please check to see if there are any I/O errors
in the log around the time the corruption message appears.
Ok, here is a test:
test:/#
On Tue, Mar 27, 2007 at 06:16:04PM +0200, Oliver Joa wrote:
> Hi,
>
> since some weeks i try to get my new hardware running:
>
> Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz
> Intel DP965LT Mainboard
> Seagate SATA-Harddisk in AHCI-Mode
>
> After some hours of running or after some heavy
On Wed, 28 Mar 2007 12:59:10 +0200
Oliver Joa <[EMAIL PROTECTED]> wrote:
> i did this already (in the first startup-script). It does not help.
>
> Another Idea?
try replacing the SATA cable...
--
Paolo Ornati
Linux 2.6.20.4 on x86_64
-
To unsubscribe from this list: send the
hi,
Paolo Ornati wrote:
[...]
What Seagate is it? (hdparm -I /dev/sda | head)
I have this one:
ATA device, with non-removable media
Model Number: ST380817AS
Serial Number: 4MR08EK8
Firmware Revision: 3.42
Model Number: ST3160827AS
On Wed, 28 Mar 2007 09:46:40 +0200
Oliver Joa <[EMAIL PROTECTED]> wrote:
> What can be wrong? There is nothing special, only board, cpu and
> harddisk, no other hardware. The board is running with the newest
> available bios. I bought a Intel-board, because normally Intel is
> supported very
On Wed, 28 Mar 2007 09:46:40 +0200
Oliver Joa [EMAIL PROTECTED] wrote:
What can be wrong? There is nothing special, only board, cpu and
harddisk, no other hardware. The board is running with the newest
available bios. I bought a Intel-board, because normally Intel is
supported very well.
hi,
Paolo Ornati wrote:
[...]
What Seagate is it? (hdparm -I /dev/sda | head)
I have this one:
ATA device, with non-removable media
Model Number: ST380817AS
Serial Number: 4MR08EK8
Firmware Revision: 3.42
Model Number: ST3160827AS
On Wed, 28 Mar 2007 12:59:10 +0200
Oliver Joa [EMAIL PROTECTED] wrote:
i did this already (in the first startup-script). It does not help.
Another Idea?
try replacing the SATA cable...
--
Paolo Ornati
Linux 2.6.20.4 on x86_64
-
To unsubscribe from this list: send the line
On Tue, Mar 27, 2007 at 06:16:04PM +0200, Oliver Joa wrote:
Hi,
since some weeks i try to get my new hardware running:
Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz
Intel DP965LT Mainboard
Seagate SATA-Harddisk in AHCI-Mode
After some hours of running or after some heavy file-i/o
Hi,
David Chinner wrote:
[...]
What is the corruption message in the log from XFS?
Can you please post that? Without it we really can't help you.
Also, please check to see if there are any I/O errors
in the log around the time the corruption message appears.
Ok, here is a test:
test:/#
Oliver Joa wrote:
Ok, here is a test:
test:/# find / -xdev | cpio -padm /test/
cpio: /usr/src/linux-2.6.20.2/Documentation/networking/NAPI_HOWTO.txt:
Structure needs cleaning
3648371 blocks
test:/#
That, cryptically enough, means that the filesystem has detected a
problem and has shut
Hi,
Eric Sandeen wrote:
[...]
For one reason or another, xfs has detected a corrupted on-disk inode
format which it cannot recognize, and shuts down. It is likely the
result of something which has gone wrong previously. xfs_repair should
fix it. Are there other non-xfs messages in your
On Wed, Mar 28, 2007 at 02:42:00PM +0200, Oliver Joa wrote:
Hi,
David Chinner wrote:
[...]
What is the corruption message in the log from XFS?
Can you please post that? Without it we really can't help you.
Also, please check to see if there are any I/O errors
in the log around the
Oliver Joa wrote:
eason or another, xfs has detected a corrupted on-disk inode format
which it cannot recognize, and shuts down. It is likely the result
of something which has gone wrong previously. xfs_repair should fix
it. Are there other non-xfs messages in your logs indicating other
Oliver Joa wrote:
eason or another, xfs has detected a corrupted on-disk inode format
which it cannot recognize, and shuts down.
Oh, one other thing that may not apply in your case, but may.
Does your SATA disk support write caching? Does it support
something called a barrier function?
Oliver Joa wrote:
I also often get a sata-bus-reset with the kernels 2.6.19.2
and 2.6.20.2.
What can I do to find the problem? I think about to change
from xfs to ext2 but the filesystemcheck every 30 mounts lasts
a long time.
Do you have any Idea?
In this whole message I can only help on
Hi,
since some weeks i try to get my new hardware running:
Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz
Intel DP965LT Mainboard
Seagate SATA-Harddisk in AHCI-Mode
After some hours of running or after some heavy file-i/o
(find / | cpio -padm /test) I always get a corrupted
XFS-filesystem.
I
Hi,
since some weeks i try to get my new hardware running:
Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz
Intel DP965LT Mainboard
Seagate SATA-Harddisk in AHCI-Mode
After some hours of running or after some heavy file-i/o
(find / | cpio -padm /test) I always get a corrupted
XFS-filesystem.
I
Oliver Joa wrote:
I also often get a sata-bus-reset with the kernels 2.6.19.2
and 2.6.20.2.
What can I do to find the problem? I think about to change
from xfs to ext2 but the filesystemcheck every 30 mounts lasts
a long time.
Do you have any Idea?
In this whole message I can only help on
32 matches
Mail list logo
