linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "G. Richard Bellamy" <rbellamy@pteradigm.com>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: fallocate fail on btrfs
Date: Wed, 27 Aug 2014 15:39:59 -0700	[thread overview]
Message-ID: <CADw2B2MJS-pkd+XfwLTpq_pqzQzLWnkzxLcaw8UYjnS-jOF25g@mail.gmail.com> (raw)
In-Reply-To: <CADw2B2NX8XY3V_vD-7eN9vj0tHtEfJwdsS4bovQ0cOHus_9Q-g@mail.gmail.com>

Also, here's the strace of the fallocate call:
http://sprunge.us/QXFN

On Wed, Aug 27, 2014 at 10:39 AM, G. Richard Bellamy
<rbellamy@pteradigm.com> wrote:
> Good questions, should have included that info in the OP.
>
> The current versions I can get, but I'm frankly terrified to try to
> roll back to prior versions to "test" this, since back in that land be
> monsters with deadlocks preventing degraded volumes from being fixed
> and other challenges I wasn't qualified to fix - and it was over three
> months ago that I tried fallocate last. I run Arch and aggressively
> update, so I can infer what those version were, and will do so, though
> I know that is of limited efficacy in helping you help me...
>
> Best-guess Prior (2014-06-30):
> ------------------------------------------------
> linux-lts 3.10.45-1
> btrfs-progs 3.14.2-2
> linux 3.15.2-1
> util-linux 2.24.2-1
>
> Current (2014-08-27 10:28:07):
> -----------
> rbellamy@eanna i ~ % pacman -Q linux-lts btrfs-progs-git linux util-linux
> linux-lts 3.14.17-1
> btrfs-progs-git 3.16_108_d34cbe7-1
> linux 3.16.1-1
> util-linux 2.25-3
>
> On Tue, Aug 26, 2014 at 11:39 PM, Duncan <1i5t5.duncan@cox.net> wrote:
>> G. Richard Bellamy posted on Tue, 26 Aug 2014 22:05:01 -0700 as excerpted:
>>
>>> When I try to run fallocate with "--keep-size" on my btrfs partitions,
>>> it's failing, and I'm at a loss as to why. This was working in prior
>>> versions.
>>>
>>> Any suggestions on how to attack this problem? I'm betting I'm missing
>>> something simple here, and have just gone down the rabbit hole...
>>>
>>> BTW, I've confirmed that the line that fails is fallocate.c:368 [2],
>>> with "open" always returning -1.
>>
>> One "something simple" you're missing (either that or I am) is any
>> reference to which version you're running.  You say it was working in
>> prior versions, but /which/ prior versions, and /which/ version doesn't
>> work now?
>>
>> --
>> 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
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2014-08-27 22:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-27  5:05 fallocate fail on btrfs G. Richard Bellamy
2014-08-27  6:39 ` Duncan
2014-08-27 17:39   ` G. Richard Bellamy
2014-08-27 22:39     ` G. Richard Bellamy [this message]
2014-08-27 22:51       ` G. Richard Bellamy
2014-08-27 22:58         ` G. Richard Bellamy
2014-08-27 23:33           ` Holger Hoffstätte
2014-08-28  9:12             ` Duncan
2014-08-28 14:48               ` G. Richard Bellamy
2014-08-28 20:10                 ` Duncan

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=CADw2B2MJS-pkd+XfwLTpq_pqzQzLWnkzxLcaw8UYjnS-jOF25g@mail.gmail.com \
    --to=rbellamy@pteradigm.com \
    --cc=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;
as well as URLs for NNTP newsgroup(s).