From: Michael Lueck <mlueck@lueckdatasystems.com>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@oss.sgi.com, Dann Frazier <dannf@debian.org>
Subject: Re: xfsdump SGI_FS_BULKSTAT errno = 22, how could this IRIX bug get into Ubuntu 10.04 Lucid between kernels 2.6.32-27 and 2.6.32-26?
Date: Tue, 08 Feb 2011 15:24:53 -0500 [thread overview]
Message-ID: <4D51A695.6060700@lueckdatasystems.com> (raw)
In-Reply-To: <4D51A0BC.6070201@lueckdatasystems.com>
[-- Attachment #1: Type: text/plain, Size: 207 bytes --]
Michael Lueck wrote:
> I will IPL the server to the latest kernel and run the tests immediately.
Here they are attached...
Sincerely,
--
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems.com/
[-- Attachment #2: xfs_db-inode_80508397.log --]
[-- Type: text/x-log, Size: 1032 bytes --]
# sudo xfs_db -c "inode 80508397" -c p /dev/sda9 2>&1 | tee xfs_db-inode_80508397.log
core.magic = 0x494e
core.mode = 040777
core.version = 2
core.format = 2 (extents)
core.nlinkv2 = 2
core.onlink = 0
core.projid = 0
core.uid = 1000
core.gid = 1000
core.flushiter = 10
core.atime.sec = Sun Feb 6 16:59:44 2011
core.atime.nsec = 088915516
core.mtime.sec = Tue Jan 11 13:50:51 2011
core.mtime.nsec = 950662167
core.ctime.sec = Tue Jan 11 13:50:51 2011
core.ctime.nsec = 950662167
core.size = 4096
core.nblocks = 1
core.extsize = 0
core.nextents = 1
core.naextents = 0
core.forkoff = 0
core.aformat = 2 (extents)
core.dmevmask = 0
core.dmstate = 0
core.newrtbm = 0
core.prealloc = 0
core.realtime = 0
core.immutable = 0
core.append = 0
core.sync = 0
core.noatime = 0
core.nodump = 0
core.rtinherit = 0
core.projinherit = 0
core.nosymlinks = 0
core.extsz = 0
core.extszinherit = 0
core.nodefrag = 0
core.filestream = 0
core.gen = 3978985788
next_unlinked = null
u.bmx[0] = [startoff,startblock,blockcount,extentflag] 0:[0,5052169,1,0]
[-- Attachment #3: xfs_repair-srv.log --]
[-- Type: text/x-log, Size: 988 bytes --]
# sudo xfs_repair -n /dev/sda9 2>&1 | tee xfs_repair-srv.log
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- scan filesystem freespace and inode maps...
- found root inode chunk
Phase 3 - for each AG...
- scan (but don't clear) agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- process newly discovered inodes...
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- check for inodes claiming duplicate blocks...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
- traversing filesystem ...
- traversal finished ...
- moving disconnected inodes to lost+found ...
Phase 7 - verify link counts...
No modify flag set, skipping filesystem flush and exiting.
[-- Attachment #4: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-02-08 20:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 13:30 xfsdump SGI_FS_BULKSTAT errno = 22, how could this IRIX bug get into Ubuntu 10.04 Lucid between kernels 2.6.32-27 and 2.6.32-26? Michael Lueck
2011-02-02 18:32 ` Bill Kendall
2011-02-02 19:03 ` Michael Lueck
2011-02-03 4:58 ` Dave Chinner
2011-02-03 14:43 ` Michael Lueck
2011-02-04 0:08 ` Dave Chinner
2011-02-04 14:12 ` Michael Lueck
2011-02-04 20:49 ` Dave Chinner
2011-02-07 20:55 ` Bill Kendall
2011-02-07 21:23 ` Dave Chinner
2011-02-07 21:42 ` Bill Kendall
2011-02-07 22:04 ` Dave Chinner
2011-02-09 1:24 ` Bill Kendall
2011-02-08 17:39 ` Michael Lueck
2011-02-08 19:52 ` Dave Chinner
2011-02-08 19:59 ` Michael Lueck
2011-02-08 20:24 ` Michael Lueck [this message]
2011-02-08 22:47 ` Dave Chinner
2011-02-14 2:52 ` Michael Lueck
2011-02-08 17:39 ` Michael Lueck
2011-02-03 14:51 ` Michael Lueck
2011-02-04 14:52 ` dann frazier
2011-04-22 12:34 ` Michael Lueck
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=4D51A695.6060700@lueckdatasystems.com \
--to=mlueck@lueckdatasystems.com \
--cc=dannf@debian.org \
--cc=david@fromorbit.com \
--cc=linux-xfs@oss.sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.