From: George Amvrosiadis <gamvrosi@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: ENOSPC issue -- plenty of free space in metadata/data chunks
Date: Sat, 31 Aug 2013 12:08:30 +0200 [thread overview]
Message-ID: <CABF9=8jix2GoAm-nA41jMYMRqv+dxGq98SkaaYDvVwcqiHiTCQ@mail.gmail.com> (raw)
Hi,
I'm using LK3.10, replaying filesystem traces on a btrfs filesystem,
and I my experiments always result in write()'s returning ENOSPC
(No space left on device). I'm baffled because I've been reading
about this issue on here, but in those other cases there were
indications that the Metadata chunks were used up. As you can
see in the attached df output, I don't have that issue. The following
fs is mounted using enospc_debug, but I haven't seen anything printed.
Can someone please let me know if there's a newer LK version
that has addressed possibly related ENOSPC issues, or whether
this is a known bug?
Many thanks,
George
gamvrosi@c154:~$ sudo btrfs fi df /media/btrfs-test
Data: total=87.01GB, used=85.48GB
System, DUP: total=8.00MB, used=16.00KB
System: total=4.00MB, used=0.00
Metadata, DUP: total=1.00GB, used=383.77MB
Metadata: total=8.00MB, used=0.00
gamvrosi@c154:~$ sudo btrfs fi sh
Label: none uuid: 9c632287-214b-4203-94e9-5411ad0d1fe0
Total devices 1 FS bytes used 85.86GB
devid 1 size 213.52GB used 89.04GB path /dev/sda3
Btrfs v0.20-rc1-253-g7854c8b-dirty
--
George Amvrosiadis, B.Sc., Ph.D. Candidate
Graduate Students' Union Representative
Computer Science, University of Toronto
reply other threads:[~2013-08-31 10:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CABF9=8jix2GoAm-nA41jMYMRqv+dxGq98SkaaYDvVwcqiHiTCQ@mail.gmail.com' \
--to=gamvrosi@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 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).