From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: enospc while having a lot of free space with kernel 4.4
Date: Sat, 13 Feb 2016 12:32:44 +0000 (UTC) [thread overview]
Message-ID: <pan$2f1b6$75e523f6$567ed9fa$5e851f19@cox.net> (raw)
In-Reply-To: 56BED257.5080107@profihost.ag
Stefan Priebe posted on Sat, 13 Feb 2016 07:51:03 +0100 as excerpted:
> while running 4.4 i got the following enospc error today:
I don't see the usual btrfs fi sh <mntpnt> and btrfs fi df <mntpnt>
output included, that would show exactly what btrfs thought the
free-space situation was.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
prev parent reply other threads:[~2016-02-13 12:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-13 6:51 enospc while having a lot of free space with kernel 4.4 Stefan Priebe
2016-02-13 12:32 ` Duncan [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='pan$2f1b6$75e523f6$567ed9fa$5e851f19@cox.net' \
--to=1i5t5.duncan@cox.net \
--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