From: Stefan Priebe <s.priebe@profihost.ag>
To: Josef Bacik <jbacik@fusionio.com>
Cc: Chris Mason <clmason@fusionio.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: No space left on device (28)
Date: Fri, 22 Mar 2013 21:55:07 +0100 [thread overview]
Message-ID: <514CC52B.1000201@profihost.ag> (raw)
In-Reply-To: <20130322204932.GE1955@localhost.localdomain>
Hi Jsoef,
thanks!
Am 22.03.2013 21:49, schrieb Josef Bacik:
> On Fri, Mar 22, 2013 at 01:10:05PM -0600, Stefan Priebe wrote:
>> Hi Josef,
>> Am 22.03.2013 16:54, schrieb Josef Bacik:
>>> On Fri, Mar 22, 2013 at 07:56:41AM -0600, Stefan Priebe - Profihost AG wrote:
>>>> Hi Josef,
>>>> Am 22.03.2013 14:53, schrieb Josef Bacik:
>>>>> On Fri, Mar 22, 2013 at 06:11:56AM -0600, Stefan Priebe - Profihost AG wrote:
>>>>>> Hi Chris,
>>>>>>
>>>>>>>>>>> Which kernel are you running?
>>>>>>>>>>>
>>>>>>>>>>> -chris
>>>>>>>>>>
>>>>>>>>>> vanilla 3.8.3.
>>>>>>>>>
>>>>>>>>> Ok, with the 3.9 merge window Josef changed how we do the reservations.
>>>>>>>>> Are you able to try a slightly more experimental kernel?
>>>>>>
>>>>>> any ideas what i can check? 3.9-rc3 gives me same results.
>>>>>>
>>>>>
>>>>> Sorry Stefan I'm almost done with what I'm working on and then I'll work up a
>>>>> patch for you to run so I can narrow down what's going on. Thanks,
>>>>
>>>> Great!
>>>>
>>>> Thanks - just wanted to know that it's not my fault. I'm happy to test
>>>> the patch and provide feedback.
>>>>
>>> Ok I think we are way over-reserving for rename, can you give this patch a whirl
>>> and see what happens? If it still fails can you capture dmesg and reply with
>>> that so I can see what's going on. Thanks,
>>
>> Thanks for the patch. I was able to copy some files and i'm still able
>> put it copy some then fails on some then copies some then fails on some.
>>
>
> Ok so I've been working on another ENOSPC related problem that I think is
> affecting you as well. So I'm going to nail that down and see if that helps you
> too, if not we'll poke around your problem some more and try and work out what's
> happening. I'll get back to this fresh Monday morning. Thanks,
>
> Josef
>
next prev parent reply other threads:[~2013-03-22 20:55 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 8:03 No space left on device (28) Stefan Priebe - Profihost AG
2013-03-21 18:00 ` Chris Mason
2013-03-21 18:35 ` Stefan Priebe - Profihost AG
2013-03-21 19:02 ` Chris Mason
2013-03-21 19:42 ` Stefan Priebe
2013-03-22 6:08 ` Stefan Priebe - Profihost AG
2013-03-22 12:11 ` Stefan Priebe - Profihost AG
2013-03-22 13:53 ` Josef Bacik
2013-03-22 13:56 ` Stefan Priebe - Profihost AG
2013-03-22 15:54 ` Josef Bacik
2013-03-22 19:10 ` Stefan Priebe
2013-03-22 20:49 ` Josef Bacik
2013-03-22 20:55 ` Stefan Priebe [this message]
2013-03-25 20:14 ` Josef Bacik
2013-03-26 7:45 ` Stefan Priebe
2013-03-26 12:53 ` Josef Bacik
2013-03-26 12:55 ` Stefan Priebe - Profihost AG
2013-03-26 13:30 ` Josef Bacik
2013-03-26 13:49 ` Stefan Priebe - Profihost AG
2013-03-26 14:44 ` Josef Bacik
2013-03-26 15:03 ` Stefan Priebe - Profihost AG
2013-03-26 15:25 ` Josef Bacik
2013-03-26 16:19 ` Stefan Priebe
2013-03-26 17:45 ` Josef Bacik
2013-03-26 19:05 ` Stefan Priebe
2013-03-26 19:16 ` Josef Bacik
2013-03-26 19:22 ` Stefan Priebe
2013-03-26 19:38 ` Josef Bacik
2013-03-26 19:47 ` Stefan Priebe
2013-03-22 6:13 ` Roman Mamedov
2013-03-22 6:24 ` cwillu
2013-03-22 6:39 ` Stefan Priebe - Profihost AG
2013-03-22 6:41 ` cwillu
2013-03-22 7:06 ` Stefan Priebe - Profihost AG
2013-03-22 6:38 ` Stefan Priebe - Profihost AG
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=514CC52B.1000201@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=clmason@fusionio.com \
--cc=jbacik@fusionio.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