Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] BUG 2.6.11-rc4-pa1 XFS data page fault
Date: Sat, 19 Feb 2005 15:27:23 -0700	[thread overview]
Message-ID: <20050219222723.GA12572@colo.lackof.org> (raw)
In-Reply-To: <20050216065539.GB5251@colo.lackof.org>

On Tue, Feb 15, 2005 at 11:55:39PM -0700, Grant Grundler wrote:
> Running 2.6.11-rc4-pa0-plus (equivalent to -pa1) on a500-65 (riot).
> xfs ran spew for 48h but panic'd when I did a "cvs up -A"
> to the CVS source tree on the same file system.

XFS behaves better with sym2+MMIO on j6000 running a 64-bit SMP kernel.
I was able to run spew several hours with no problems.
This is without the patch that Joel pointed out from the -mm tree.

This suggests there is a problem with Astro/Elroy programming
where "Sprockets" firmware (for Astro based workstations) does
something different than PAT PDC firmware on a500.
I'm investigating.


However, did see one "WARN_ON" when I rsync (/home to /home2):
root@gggj6k:/home# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sda3              1783984   1522420    170940  90% /
tmpfs                  4110708         0   4110708   0% /dev/shm
/dev/sda4             15439312  13086812   1568220  90% /home
/dev/sdb3             17019904   5155384  11864520  31% /mnt
/dev/sdb4             17773568  12486340   5287228  71% /home2

root@gggj6k:/home# lsscsi
[1:0:5:0]    disk    SEAGATE  ST318203LC       0001  /dev/sda
[1:0:6:0]    disk    FUJITSU  MAJ3364MC        HP12  /dev/sdb

The rsync completed but one error showed up 4 times on the console
during the second half (about) of the rsync:

Filesystem "sdb4": XFS internal error xfs_btree_check_sblock at line 342 of file fs/xfs/xfs_btree.c.  Caller 0x00000000102f1b84
Backtrace:
 [<00000000101145e0>] dump_stack+0x18/0x28
 [<00000000102eceac>] xfs_error_report+0x64/0x70
 [<00000000102d7718>] xfs_btree_check_sblock+0x78/0xf8
 [<00000000102f1b84>] xfs_inobt_lookup+0x144/0x3a0
 [<00000000102f3514>] xfs_inobt_lookup_le+0x24/0x30
 [<00000000102f08f0>] xfs_dialloc+0xe90/0x12e0
 [<00000000102f6638>] xfs_ialloc+0x70/0x4e0
 [<0000000010310a10>] xfs_dir_ialloc+0xb8/0x3e8
 [<0000000010316d30>] xfs_create+0x2f0/0x810
 [<0000000010326140>] linvfs_mknod+0x1e0/0x298
 [<000000001032620c>] linvfs_create+0x14/0x20
 [<00000000101d3c04>] vfs_create+0xbc/0xf8
 [<00000000101d4a30>] open_namei+0xb58/0xc10
 [<00000000101b5b14>] filp_open+0x44/0x98
 [<00000000101b5f98>] sys_open+0x98/0x110
 [<0000000010107fac>] syscall_exit+0x0/0x14


Perhaps this is fixed in the patches; I haven't looked.

hth,
grant
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  parent reply	other threads:[~2005-02-19 22:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-16  6:55 [parisc-linux] BUG 2.6.11-rc4-pa1 XFS data page fault Grant Grundler
     [not found] ` <4208D51500003293@mail-5-bnl.tiscali.it>
2005-02-16  7:45   ` Grant Grundler
2005-02-17  4:06 ` Carlos O'Donell
2005-02-19 22:27 ` Grant Grundler [this message]
2005-02-21  0:04   ` Grant Grundler
     [not found] <42075CE800004656@mail-6-bnl.tiscali.it>
     [not found] ` <200502170653.52415.mszick@wolfbutter.com>
     [not found]   ` <20050217210915.GB1081@colo.lackof.org>
2005-02-18  1:00     ` Michael S. Zick
2005-02-18  6:23   ` Grant Grundler
2005-02-18  9:28     ` Thibaut VARENE
2005-02-18 14:07       ` Michael S. Zick
     [not found]       ` <20050219022808.GA28925@colo.lackof.org>
2005-02-19 10:17         ` Michael S. Zick
2005-02-21 16:58           ` Matthew Wilcox
  -- strict thread matches above, loose matches on Subject: below --
2005-02-18 17:35 Joel Soete

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=20050219222723.GA12572@colo.lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=parisc-linux@lists.parisc-linux.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