All of lore.kernel.org
 help / color / mirror / Atom feed
From: nightrow <nightrow@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: BUG: btrfsck segfaults on regular file
Date: Wed, 29 Apr 2009 21:19:56 +0000 (UTC)	[thread overview]
Message-ID: <loom.20090429T211105-898@post.gmane.org> (raw)

I just tried running btrsfck without enough right to open the device, i got the
same : a segfault. I also got the segfault taking a unknow device.

Please display a message like : "Unknow device or file, you may not have enough
rights to open it"


             reply	other threads:[~2009-04-29 21:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-29 21:19 nightrow [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-01-19 18:16 BUG: btrfsck segfaults on regular file Zach Carter
2009-01-21  2:10 ` Shen Feng

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=loom.20090429T211105-898@post.gmane.org \
    --to=nightrow@gmail.com \
    --cc=linux-btrfs@vger.kernel.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 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.