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
Hi there,
What XFS blocksize are you using, and what is your page size?
There are known issues when using blocksizes smaller than the
page size in the 2.6 XFS code at the moment.
Feel free to open bugs for this and your repair problems on the
XFS site on oss.sgi.com; the gdb backtrace of the failed repair
attempts will be useful as well.
thanks.
On Fri, Aug 01, 2003 at 04:31:55AM +0200, Mariusz Zielinski wrote:
> 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
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Nathan
On Thu, 2003-07-31 at 22:40, Nathan Scott wrote:
> Hi there,
>
> What XFS blocksize are you using, and what is your page size?
> There are known issues when using blocksizes smaller than the
> page size in the 2.6 XFS code at the moment.
>
> Feel free to open bugs for this and your repair problems on the
> XFS site on oss.sgi.com; the gdb backtrace of the failed repair
> attempts will be useful as well.
I believe there was a post this past weekend about block sizes (or maybe
fragment sizes) on the Opteron. It wasn't with XFS I'm pretty sure. I
tried searching for it, but can't find it again.
I'm going to start playing with an Opteron pretty soon. I will be using
XFS. What are the recommended settings when creating file systems?
--
Chris
>
>Hi there,
>
>What XFS blocksize are you using, and what is your page size?
>There are known issues when using blocksizes smaller than the
>page size in the 2.6 XFS code at the moment.
>
Hi Nathan, and congratilations for the SGI work.
Now i have a Mandrake with the 2.5.75 kernel and XFS in
all partitions. The filesystem looks work very well.
I am planning install 2.6.0-test3 when it comes and i wanna
ask you: how can i know what blocksize am i using?, and how
know what is the page size in my system?.
Thanks you, very much, in advance.
Regards.
Jose.
http://linuxespana.scripterz.org
FreeBSD RELEASE 4.8.
Mandrake Linux 9.1 Kernel 2.5.75 XFS.
Registered BSD User 51101.
Registered Linux User #213309.
Memories..... You are talking about memories.
Rick Deckard. Blade Runner.
Get your Free E-mail at http://chevy.zzn.com
___________________________________________________________
Get your own Web-based E-mail Service at http://www.zzn.com
On Fri, 2003-08-01 at 02:58, Jose Luis Alarcon wrote:
> >
> >Hi there,
> >
> >What XFS blocksize are you using, and what is your page size?
> >There are known issues when using blocksizes smaller than the
> >page size in the 2.6 XFS code at the moment.
> >
>
> Hi Nathan, and congratilations for the SGI work.
>
> Now i have a Mandrake with the 2.5.75 kernel and XFS in
> all partitions. The filesystem looks work very well.
>
> I am planning install 2.6.0-test3 when it comes and i wanna
> ask you: how can i know what blocksize am i using?, and how
> know what is the page size in my system?.
>
> Thanks you, very much, in advance.
>
> Regards.
>
> Jose.
Use the xfs_info command on a mount point:
meta-data=/xfs isize=256 agcount=8, agsize=131031
blks
= sectsz=512
data = bsize=4096 blocks=1048241, imaxpct=25
= sunit=0 swidth=0 blks, unwritten=1
naming =version 2 bsize=4096
log =internal bsize=4096 blocks=16384, version=1
= sectsz=512 sunit=0 blks
realtime =none extsz=65536 blocks=0, rtextents=0
bsize=4096 is the vlock size.
Steve
--
Steve Lord voice: +1-651-683-3511
Principal Engineer, Filesystem Software email: [email protected]