From: Felix Blanke <felixblanke@gmail.com>
To: "Bernhard Rosenkraenzer" <bero@arklinux.ch>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: mkfs.btrfs doesn't work inside loopback mounted chroot jails: error checking /dev/sda3 mount status
Date: Fri, 4 Feb 2011 10:51:52 +0100 [thread overview]
Message-ID: <20110204105152.0000151d@unknown> (raw)
In-Reply-To: <2b8c-4d4bc900-1-18251900@152037387>
Hi,
you should search the mailinglist before you write patches :)
That problem is known and a patch is available:
https://patchwork.kernel.org/patch/449001/
But it isn't in the btrfs-progs git yet.
Regards,
Felix
Am Fri, 04 Feb 2011 10:38:25 +0100
schrieb "Bernhard Rosenkraenzer" <bero@arklinux.ch>:
> Hi,
> mkfs.btrfs aborts unconditionally with "error checking [whatever]
> mount status" under some circumstances.
>
> I'm running into it when using a live CD that boots from a minimal CD
> image, then does
>
> mount -o loop -t squashfs /squashfs.img /mnt/realsystem
> chroot /mnt/realsystem
> [stuff you actually want to do here]
>
> strace shows mkfs.btrfs aborting after trying to
>
> lstat("/squashfs.img", 0x7fff2c712c90) = -1 ENOENT (No such file or
> directory)
>
> [obviously, it can't access /squashfs.img after chroot]
>
>
> I'm attaching a "fix" that allows circumventing the problem with a
> --force switch, patch is relative to "next" branch in git. I'm also
> adding this patch to the Ark Linux package of btrfs-progs unless
> someone screams very loudly. ;)
>
> ttyl
> bero
prev parent reply other threads:[~2011-02-04 9:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 9:38 mkfs.btrfs doesn't work inside loopback mounted chroot jails: error checking /dev/sda3 mount status Bernhard Rosenkraenzer
2011-02-04 9:51 ` Felix Blanke [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=20110204105152.0000151d@unknown \
--to=felixblanke@gmail.com \
--cc=bero@arklinux.ch \
--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.