linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: Anand Jain <anand.jain@oracle.com>
Cc: Liu Bo <bo.li.liu@oracle.com>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs check --repair is clean, but mount fails
Date: Sat, 27 Feb 2016 19:09:30 -0800	[thread overview]
Message-ID: <20160228030930.GS19699@merlins.org> (raw)
In-Reply-To: <56D25104.9020107@oracle.com>

On Sun, Feb 28, 2016 at 09:44:36AM +0800, Anand Jain wrote:
> 
> Marc,
> 
> > Err, I'm very perplexed now. I already have a scan in my boot process
> > after device decrypts.
> > Somehow it saw one of my 2 devices, but not the other one?
> 
> If blkid shows both the devices and if you are running 'btrfs dev scan'
> during boot, then yes kernel should see both the devices.
 
Agreed. It has every single time except that one time.

> Just to be sure, Can you reconfirm if the below blkid output is taken
> at the time of the bootup where you are running btrfs dev scan in the
> script ?

It's taken after the problem was fixed with a 2nd btrfs scan. It's a
server doing a 3 day long copy. Can't reboot it right now :)

> If you have a choice pls add, 'btrfs fi show -d' as well for the outputs
> to be taken at the time of boot just before system's 'btrfs dev scan',

I'll do that next time, thanks.

> Pls do share your /etc/fstab output for /var/local/space (I guess
> you don't have -o degrade option) which is good for this debugging,
> which means mount fails if any one of the device is missing.

Nothing fancy:
LABEL=btrfs_space      /var/local/space btrfs   subvol=varlocalspace,defaults,compress=lzo,skip_balance,noatime,noexec 0 0

I'll do more debugging if it happens agian, but I'm pretty sure it was a
one time thing.
Next boot will tell :)

Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/                         | PGP 1024R/763BE901

  reply	other threads:[~2016-02-28  3:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-27  2:39 btrfs check --repair is clean, but mount fails Marc MERLIN
2016-02-27  2:45 ` Liu Bo
2016-02-27  3:03   ` Marc MERLIN
2016-02-27 18:06     ` Liu Bo
2016-02-28  1:04       ` Marc MERLIN
2016-02-27 22:58     ` Anand Jain
2016-02-28  0:56       ` Marc MERLIN
2016-02-28  1:44         ` Anand Jain
2016-02-28  3:09           ` Marc MERLIN [this message]
2016-02-28  6:49             ` Duncan
2016-02-28 13:56               ` Marc MERLIN
2016-02-28  5:17           ` Marc MERLIN
2016-02-28  6:11             ` Anand Jain

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=20160228030930.GS19699@merlins.org \
    --to=marc@merlins.org \
    --cc=anand.jain@oracle.com \
    --cc=bo.li.liu@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).