All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jay Ashworth <jra@baylink.com>
To: xfs@oss.sgi.com
Subject: Re: XFS filesystem triggering assert in _repair 3.1.11
Date: Mon, 15 Jul 2013 00:41:11 -0400 (EDT)	[thread overview]
Message-ID: <20537712.1400.1373863270994.JavaMail.root@benjamin.baylink.com> (raw)
In-Reply-To: <20130715000748.GD5228@dastard>

----- Original Message -----
> From: "Dave Chinner" <david@fromorbit.com>

> > > xfs_db> type bmapbt
> >
> > Well, the manpage says that's a type, but my xfs_db, v 3.1.11, says
> > it's not. Huh?
> 
> bmapbtd. "d" mens data fork. bmapbta is for the attribute fork....

Oddly, the manpage I was looking at listed just the one, without the suffixes.

> > I hate power supplies.
> 
> I'd be spending a few dollars to get a new one ;)

The old one was a $100 Antec 650 that lasted nearly 7 solid years; I'm
not feeling too badly about it.  It's been replaced by a Corsair; we'll see
how that plays in Peoria.

Cheers,
-- jra
-- 
Jay R. Ashworth                  Baylink                       jra@baylink.com
Designer                     The Things I Think                       RFC 2100
Ashworth & Associates     http://baylink.pitas.com         2000 Land Rover DII
St Petersburg FL USA               #natog                      +1 727 647 1274

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2013-07-15  4:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <18642856.1344.1373749779825.JavaMail.root@benjamin.baylink.com>
2013-07-13 21:29 ` XFS filesystem triggering assert in _repair 3.1.11 Jay Ashworth
2013-07-14 15:51   ` Eric Sandeen
2013-07-14 16:14     ` Jay Ashworth
2013-07-15  0:07       ` Dave Chinner
2013-07-15  4:41         ` Jay Ashworth [this message]

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=20537712.1400.1373863270994.JavaMail.root@benjamin.baylink.com \
    --to=jra@baylink.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 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.