From: Stephane CHAZELAS <stephane_chazelas@yahoo.fr>
To: linux-btrfs@vger.kernel.org
Subject: ENOSPC on almost empty FS
Date: Tue, 1 Nov 2011 08:36:12 +0000 (UTC) [thread overview]
Message-ID: <slrnjavbrs.81n.stephane.chazelas@spam.is.invalid> (raw)
Hiya,
trying to restore a FS from a backup (tgz) on a freshly made
btrfs this morning, I got ENOSPCs after about 100MB out of 4GB
have been extracted. strace indicates that the ENOSPC are upon
the open(O_WRONLY).
Restoring with:
mkfs.btrfs /dev/mapper/VG_USB-root
mount -o compress-force,ssd $_ /mnt
cd /mnt
pv ~/backup.tgz | gunzip | sudo bsdtar -xpSf - --numeric-owner
That's on a LVM LV with the PV on a USB key.
If I supspend the job and resume it, then the ENOSPCs go away.
The only way I could restore the backup was via rate limiting
the untar:
zcat ~/backup.tgz | pv -L 3000000 | sudo bsdtar -xpSf - --numeric-owner
That 3MB/s wasn't even enough, as 3 files triggered a ENOSPC,
but I did untar them separately afterwards.
That's with debian's 3.0.0-1 amd64 kernel.
Is that expected behavior due to the way allocation works in
btrfs?
--
Stephane
next reply other threads:[~2011-11-01 8:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 8:36 Stephane CHAZELAS [this message]
2011-11-01 14:01 ` ENOSPC on almost empty FS Mitch Harder
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=slrnjavbrs.81n.stephane.chazelas@spam.is.invalid \
--to=stephane_chazelas@yahoo.fr \
--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