From: Mariusz Zielinski <mzielinski@wp-sa.pl>
To: linux-kernel@vger.kernel.org
Subject: xfs problems (2.6.0-test2)
Date: Fri, 01 Aug 2003 04:31:55 +0200 [thread overview]
Message-ID: <200308010431.56108.mzielinski@wp-sa.pl> (raw)
0x0: 41 42 54 43 00 00 00 3a ff ff ff ff ff ff ff ff
Filesystem "hda3": XFS internal error xfs_da_do_buf(2) at line 2281 of file
fs/xfs/xfs_da_btree.c. Caller 0xc02042cc
Call Trace:
[<c0203e98>] xfs_da_do_buf+0x548/0x900
[<c02042cc>] xfs_da_read_buf+0x3c/0x40
[<c02042cc>] xfs_da_read_buf+0x3c/0x40
[<c02042cc>] xfs_da_read_buf+0x3c/0x40
[<c0207ab7>] xfs_dir2_block_getdents+0x87/0x2f0
[<c0207ab7>] xfs_dir2_block_getdents+0x87/0x2f0
[<c01733c6>] d_splice_alias+0x36/0x120
[<c0244c00>] linvfs_lookup+0x60/0x90
[<c01f6f59>] xfs_bmap_last_offset+0xa9/0x120
[<c0206ea0>] xfs_dir2_put_dirent64_direct+0x0/0xa0
[<c0206dcd>] xfs_dir2_isblock+0x1d/0x80
[<c0206ea0>] xfs_dir2_put_dirent64_direct+0x0/0xa0
[<c0206625>] xfs_dir2_getdents+0x95/0x160
[<c0206ea0>] xfs_dir2_put_dirent64_direct+0x0/0xa0
[<c023a662>] xfs_readdir+0x52/0x90
[<c02414bd>] linvfs_readdir+0xed/0x220
[<c016d52e>] vfs_readdir+0x5e/0x70
[<c016d830>] filldir64+0x0/0x130
[<c016d9e1>] sys_getdents64+0x81/0xbb
[<c016d830>] filldir64+0x0/0x130
[<c0109297>] syscall_call+0x7/0xb
I lost some files; even those not used for a long time.
It is possible that last shutdown was unclear.
After xfs_repair I got lost+found full of files deleted some time ago.
I actually had to run xfs_repair (2.5.3) few times because it was
'segfaulting'.
>From dmesg:
...
CPU0: Centaur VIA Ezra stepping 08
...
Local APIC not detected. Using dummy APIC emulation.
...
SGI XFS for Linux 2.6.0-test2 with ACLs, realtime, no debug enabled
SGI XFS Quota Management subsystem
...
VP_IDE: IDE controller at PCI slot 0000:00:11.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: VIA vt8231 (rev 10) IDE UDMA100 controller on pci0000:00:11.1
ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:pio, hdd:pio
hda: Maxtor 4G160J8, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: max request size: 1024KiB
hda: host protected area => 1
hda: 320173056 sectors (163929 MB) w/2048KiB Cache, CHS=19929/255/63,
UDMA(100)
/dev/ide/host0/bus0/target0/lun0: p1 p2 p3
--
Mariusz Zielinski
next reply other threads:[~2003-08-01 0:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-01 2:31 Mariusz Zielinski [this message]
2003-08-01 2:40 ` xfs problems (2.6.0-test2) Nathan Scott
2003-08-01 4:38 ` Chris Meadors
2003-08-01 7:58 Jose Luis Alarcon
2003-08-01 13:55 ` Steve Lord
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200308010431.56108.mzielinski@wp-sa.pl \
--to=mzielinski@wp-sa.pl \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).