Skip to contentSkip to conversation

Huge problem with XFS/iCH7R

DISCUSSION Carsten Otto 4 participants 8 messages Jul 2, 2006 – Jul 16, 2006

lore
Share & tools
lore
#0 lore raw

Hi there!

(System specs below)

Short summary:
System (with software raid 5, XFS, four disks connected to AHCI controller) crashes very often and loses data.

My system crashes every few days, at the moment daily. The message shown is (the drive changes about every time, I do not see a pattern here):
---
ata4: handling error/timeout
ata4: port reset, p_is 0 is 0 pis 0 cmd c017 tf 7f ss 0 se 0
ata4: status=0x50 { DriveReady SeekComplete }
sdd: Current: sense key=0x0

	ASC=0x0 ASCQ=0x0

Info fid=0x0
---
Although according to this message only one of four drives failed (in software RAID5) the system does not do anything useful. Hitting enter at the login prompt does cause the password prompt to appear and no service responds.

If I do a soft reset (using Magic Key u, then b) the BIOS does not detect exactly one drive (which is the one shown in the error message I guess). After a hard reset all drives are found, but I have to do a raid resync and xfs_repair (at least, sometimes the raid needs to be tricked into starting).

This problem occured with all kernels (all vanilla), starting with 2.6.16.something up to 2.6.17.2.
I checked all four drives with a Maxtor tool, all drives are fine. The temperature is not a problem, all drives are stable at about 35�C. I replaced the SATA cables several times.

Some images showing the errors on screen are here:
http://c-otto.de/fehler/

I'd like to know what component causes this problem and how I can solve it.

Please tell me if you need further information!

System specs:
- Intel iCH7R on Foxconn 945P7AA-EKRS2
- Pentium D 805 (2.66 GHz, 1MB Cache, Dual Core)
- 4x Maxtor 7V300F0 (MaXLine Plus III 300 GB; Sata 2; 16 MB Cache)
- 2 GB RAM

PS: Please include me in CC as I do not read the whole LKML.

Thanks a lot,

Signature · 3 lines
Carsten Otto
[email protected]
www.c-otto.de
#1 lore raw
Quoted 4 lines · Carsten Otto

If I do a soft reset (using Magic Key u, then b) the BIOS does not detect exactly one drive (which is the one shown in the error message I guess). After a hard reset all drives are found, but I have to do a raid resync and xfs_repair (at least, sometimes the raid needs to be tricked into starting).

I forgot to add:
Even after a xfs_repair sometimes another directly following run of xfs_check or xfs_repair finds errors.
Currently I have problems deleting files from lost+found:
rm: cannot remove directory `lost+found//2171932973': Directory not empty
I ran xfs_check only a few hours ago and it did not show any output (which is good).

Signature · 3 lines
Carsten Otto
[email protected]
www.c-otto.de
#2 lore raw

Adding cc,

Quoted 4 lines
Quoted 4 lines

If I do a soft reset (using Magic Key u, then b) the BIOS does not detect exactly one drive (which is the one shown in the error message I guess). After a hard reset all drives are found, but I have to do a raid resync and xfs_repair (at least, sometimes the raid needs to be tricked into starting).

But at best, RAID5 should give you the safety that you can continue working with one disk less and not worry about the filesystem. Sounds like a double bug.

Quoted 6 lines

I forgot to add:
Even after a xfs_repair sometimes another directly following run of xfs_check or xfs_repair finds errors.
Currently I have problems deleting files from lost+found:
rm: cannot remove directory `lost+found//2171932973': Directory not empty

XFS devs: possibly related the ominous 16777216 thing?

Quoted 52 lines

I ran xfs_check only a few hours ago and it did not show any output (which is good).

Quoted 49 lines

Hi there!

(System specs below)

Short summary:
System (with software raid 5, XFS, four disks connected to AHCI controller) crashes very often and loses data.

My system crashes every few days, at the moment daily. The message shown is (the drive changes about every time, I do not see a pattern here):
---
ata4: handling error/timeout
ata4: port reset, p_is 0 is 0 pis 0 cmd c017 tf 7f ss 0 se 0
ata4: status=0x50 { DriveReady SeekComplete }
sdd: Current: sense key=0x0

	ASC=0x0 ASCQ=0x0

Info fid=0x0
---
Although according to this message only one of four drives failed (in software RAID5) the system does not do anything useful. Hitting enter at the login prompt does cause the password prompt to appear and no service responds.

If I do a soft reset (using Magic Key u, then b) the BIOS does not detect exactly one drive (which is the one shown in the error message I guess). After a hard reset all drives are found, but I have to do a raid resync and xfs_repair (at least, sometimes the raid needs to be tricked into starting).

This problem occured with all kernels (all vanilla), starting with 2.6.16.something up to 2.6.17.2.
I checked all four drives with a Maxtor tool, all drives are fine. The temperature is not a problem, all drives are stable at about 35C. I replaced the SATA cables several times.

Some images showing the errors on screen are here:
http://c-otto.de/fehler/

I'd like to know what component causes this problem and how I can solve it.

Please tell me if you need further information!

System specs:
- Intel iCH7R on Foxconn 945P7AA-EKRS2
- Pentium D 805 (2.66 GHz, 1MB Cache, Dual Core)
- 4x Maxtor 7V300F0 (MaXLine Plus III 300 GB; Sata 2; 16 MB Cache)
- 2 GB RAM

PS: Please include me in CC as I do not read the whole LKML.

Jan Engelhardt

#3 lore raw
In reply to Carsten Otto
Quoted 15 lines · Carsten Otto

Hi there!

(System specs below)

Short summary:
System (with software raid 5, XFS, four disks connected to AHCI controller) crashes very often and loses data.

My system crashes every few days, at the moment daily. The message shown is (the drive changes about every time, I do not see a pattern here):
---
ata4: handling error/timeout
ata4: port reset, p_is 0 is 0 pis 0 cmd c017 tf 7f ss 0 se 0
ata4: status=0x50 { DriveReady SeekComplete }
sdd: Current: sense key=0x0

Quoted 2 lines
	ASC=0x0 ASCQ=0x0

Info fid=0x0

FWIW, the above look like hardware/driver problems.

Quoted 1 line

http://c-otto.de/fehler/

Your first issue there is the XFS dir2 regression discussed recently here and on [email protected] - there's a patch available for that and it's likely to be included in the next -stable release.

Quoted 2 lines

I'd like to know what component causes this problem and how I can solve it.

The initial problem (above) and three-of-four of your photos look unrelated to XFS, but that first image is indicating a (now fixed) XFS problem - so, looks like you have multiple issues there.

cheers.

Signature · 1 line
Nathan
#4 lore raw
Quoted 19 lines · Nathan Scott
Quoted 15 lines · Carsten Otto

Hi there!

(System specs below)

Short summary:
System (with software raid 5, XFS, four disks connected to AHCI controller) crashes very often and loses data.

My system crashes every few days, at the moment daily. The message shown is (the drive changes about every time, I do not see a pattern here):
---
ata4: handling error/timeout
ata4: port reset, p_is 0 is 0 pis 0 cmd c017 tf 7f ss 0 se 0
ata4: status=0x50 { DriveReady SeekComplete }
sdd: Current: sense key=0x0

Quoted 2 lines
	ASC=0x0 ASCQ=0x0

Info fid=0x0

Quoted 1 line

FWIW, the above look like hardware/driver problems.

If the problem doesn't occur before 2.6.16, that makes a hardware problem less likely. It's not impossible that some buggy feature is now used, but lower probability than the kernel change being the culprit. The bug fix you mention may solve the whole thing, or make it easier to debug.

General comment: if a kernel version made my system crash once a day I sure wouldn't be using it. New features are neat, but I wouldn't put up with that if it made my cat pee holy water.

I would test proposed fixes, of course, but only until I got more info for developers.

Signature · 5 lines
Bill Davidsen <[email protected]>
  Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a
normal user and is setuid root, with the "vi" line edit mode selected,
and the character set is "big5," an off-by-one errors occurs during
wildcard (glob) expansion.
#5 lore raw
Quoted 10 lines · Bill Davidsen
Quoted 10 lines
Quoted 9 lines

My system crashes every few days, at the moment daily. The message shown is (the drive changes about every time, I do not see a pattern here):
---
ata4: handling error/timeout
ata4: port reset, p_is 0 is 0 pis 0 cmd c017 tf 7f ss 0 se 0
ata4: status=0x50 { DriveReady SeekComplete }
sdd: Current: sense key=0x0

	ASC=0x0 ASCQ=0x0

Info fid=0x0

Quoted 5 lines
Quoted 1 line

FWIW, the above look like hardware/driver problems.

If the problem doesn't occur before 2.6.16, that makes a hardware problem less likely. It's not impossible that some buggy feature is now used, but lower probability than the kernel change being the culprit.

*nod*.

Quoted 1 line

The bug fix you mention may solve the whole thing, or make it easier to

I'm certain it wont; that was an XFS problem, and I can see no way it could cause device/driver issues also.

Quoted 2 lines

General comment: if a kernel version made my system crash once a day I sure wouldn't be using it.

Heh, yes - by definition.

Quoted 2 lines

New features are neat, but I wouldn't put up
with that if it made my cat pee holy water.

Not sure what new features you're talking about here? Nor how your cat fits into all this.. ;)

cheers.

Signature · 1 line
Nathan
#6 lore raw
Quoted 6 lines · Nathan Scott
Quoted 1 line · Bill Davidsen

New features are neat, but I wouldn't put up with that if it made my cat pee holy water.

Not sure what new features you're talking about here? Nor how your cat fits into all this.. ;)

Presumably the new features which required or encouraged a kernel upgrade. Why else would anyone ever mess with a working system? I count bugfixes and performance enhancements as new features for this discussion, some improvement to justify change.

Signature · 5 lines
Bill Davidsen <[email protected]>
  Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a
normal user and is setuid root, with the "vi" line edit mode selected,
and the character set is "big5," an off-by-one errors occurs during
wildcard (glob) expansion.
#7 lore raw
In reply to Carsten Otto
Quoted 2 lines · Carsten Otto

System (with software raid 5, XFS, four disks connected to AHCI controller) crashes very often and loses data.

An underdimensioned power supply was the main problem (and a XFS bug killed some files).

Signature · 3 lines
Carsten Otto
[email protected]
www.c-otto.de