From: peyytmek@gmx.de
To: Timothy Shimmin <tes@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: Fwd: Re: xfs mounting problem, hdb1 just freezes
Date: Fri, 20 Oct 2006 14:40:52 +0000 [thread overview]
Message-ID: <200610201440.52934.peyytmek@gmx.de> (raw)
In-Reply-To: <93BCAC8A8F8B13AB0095C1B8@timothy-shimmins-power-mac-g5.local>
On Friday 20 October 2006 04:06, Timothy Shimmin wrote:
> > Hello.
> > Thanks for your answer.
> >
> > That's what i have: dmesg print with kernel-2.6.16-gentoo-r3 and an print
> > of xfs_bg.
> >
> >> You could print out the offending inode with xfs_db to show us
> >> what it looks like: $xfs_db -r /dev/hdb1 -c "inode 950759" -c "print".
> >
> > I don't know what you mean with it but i added it anyway. (done with
> > kernel-2.6.18-gentoo if it matters)
> >
> > xfs_db:
> >
> > CLX ~ # xfs_db -r /dev/hdb1 -c "inode 950759" -c "print"
> > core.magic = 0x494e
> > core.mode = 0100644
> > core.version = 1
> > core.format = 3 (btree)
> > core.nlinkv1 = 0
> > core.uid = 1000
> > core.gid = 100
> > core.flushiter = 0
> > core.atime.sec = Sun Aug 27 14:56:52 2006
> > core.atime.nsec = 657389250
> > core.mtime.sec = Sun Aug 27 16:29:40 2006
> > core.mtime.nsec = 080196250
> > core.ctime.sec = Thu Oct 5 01:17:40 2006
> > core.ctime.nsec = 976565958
> > core.size = 32071862
> > core.nblocks = 7833
> > core.extsize = 0
> > core.nextents = 28
> > 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.gen = 0
> > next_unlinked = null
> > u.bmbt.level = 1
> > u.bmbt.numrecs = 1
> > u.bmbt.keys[1] = [startoff] 1:[0]
> > u.bmbt.ptrs[1] = 1:185933
>
> And now:
>
> xfs_db -r /dev/hadb1 -c "fsb 185933" -c "type bmapbtd" -c "p"
>
> to look at the 28 extent records.
>
> --Tim
Hello, thanks again for your fast answer
Sorry for the double post last time.
here it comes
CLX ~ # xfs_db -r /dev/hdb1 -c "fsb 185933" -c "type bmapbtd" -c "p"
magic = 0x424d4150
level = 0
numrecs = 27
leftsib = null
rightsib = null
recs[1-27] = [startoff,startblock,blockcount,extentflag] 1:[0,185637,16,0] 2:
[16,185537,8,0] 3:[24,185718,8,0] 4:[32,185706,8,0] 5:[40,185836,8,0] 6:
[48,185848,16,0] 7:[64,185865,16,0] 8:[80,185882,8,0] 9:[96,185899,16,0] 10:
[112,185916,16,0] 11:[340,185934,2,0] 12:[342,4768704,1320,0] 13:
[1662,4770389,239,0] 14:[1901,4770919,264,0] 15:[2165,4771391,165,0] 16:
[2330,4771860,227,0] 17:[2557,4861204,351,0] 18:[2908,4861800,257,0] 19:
[3165,4862282,349,0] 20:[3514,4862934,230,0] 21:[3744,4863506,383,0] 22:
[4127,4864141,348,0] 23:[4475,4864871,228,0] 24:[4703,4865358,268,0] 25:
[4971,4865882,593,0] 26:[5564,4866818,339,0] 27:[5903,4867729,1928,0]
next prev parent reply other threads:[~2006-10-20 12:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 14:36 Fwd: Re: xfs mounting problem, hdb1 just freezes peyytmek
2006-10-20 4:06 ` Timothy Shimmin
2006-10-20 14:40 ` peyytmek [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-19 14:35 peyytmek
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=200610201440.52934.peyytmek@gmx.de \
--to=peyytmek@gmx.de \
--cc=tes@sgi.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox