diff mbox

No space left on device (28)

Message ID 20130322155453.GD1955@localhost.localdomain (mailing list archive)
State New, archived
Headers show

Commit Message

Josef Bacik March 22, 2013, 3:54 p.m. UTC
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,

Josef

Comments

Stefan Priebe - Profihost AG March 22, 2013, 7:10 p.m. UTC | #1
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.

Rsync output:
.software/kernel/linux-3.9-rc3/drivers/rtc/rtc-wm8350.c
        12156 100%   11.17kB/s    0:00:01 (xfer#21395, to-check=1008/52625)
.software/kernel/linux-3.9-rc3/drivers/rtc/rtc-x1205.c
        16460 100%   15.05kB/s    0:00:01 (xfer#21396, to-check=1007/52625)
.software/kernel/linux-3.9-rc3/drivers/rtc/systohc.c
         1223 100%    1.12kB/s    0:00:01 (xfer#21397, to-check=1006/52625)
.software/kernel/linux-3.9-rc3/drivers/s390/
.software/kernel/linux-3.9-rc3/drivers/s390/Makefile
          144 100%    0.13kB/s    0:00:01 (xfer#21398, to-check=1052/52672)
.software/kernel/linux-3.9-rc3/drivers/s390/block/
rsync: recv_generator: mkdir 
"/mnt/.software/kernel/linux-3.9-rc3/drivers/s390/block" failed: No 
space left on device (28)
*** Skipping any contents from this failed directory ***
.software/kernel/linux-3.9-rc3/drivers/s390/char/
rsync: recv_generator: mkdir 
"/mnt/.software/kernel/linux-3.9-rc3/drivers/s390/char" failed: No space 
left on device (28)
*** Skipping any contents from this failed directory ***
.software/kernel/linux-3.9-rc3/drivers/s390/cio/
rsync: recv_generator: mkdir 
"/mnt/.software/kernel/linux-3.9-rc3/drivers/s390/cio" failed: No space 
left on device (28)
rsync: mkstemp 
"/mnt/.software/kernel/linux-3.9-rc3/drivers/regulator/.88pm8607.c.YBi0Rz" 
failed: No space left on device (28)
*** Skipping any contents from this failed directory ***
.software/kernel/linux-3.9-rc3/drivers/s390/crypto/
rsync: recv_generator: mkdir 
"/mnt/.software/kernel/linux-3.9-rc3/drivers/s390/crypto" failed: No 
space left on device (28)
*** Skipping any contents from this failed directory ***
.software/kernel/linux-3.9-rc3/drivers/s390/kvm/
rsync: recv_generator: mkdir 
"/mnt/.software/kernel/linux-3.9-rc3/drivers/s390/kvm" failed: No space 
left on device (28)
*** Skipping any contents from this failed directory ***
.software/kernel/linux-3.9-rc3/drivers/s390/net/
rsync: recv_generator: mkdir 
"/mnt/.software/kernel/linux-3.9-rc3/drivers/s390/net" failed: No space 
left on device (28)
rsync: mkstemp 
"/mnt/.software/kernel/linux-3.9-rc3/drivers/regulator/.Kconfig.0lsfuE" 
failed: No space left on device (28)
*** Skipping any contents from this failed directory ***
rsync: mkstemp 
"/mnt/.software/kernel/linux-3.9-rc3/drivers/regulator/.Makefile.C9wI7I" 
failed: No space left on device (28)
.software/kernel/linux-3.9-rc3/drivers/s390/scsi/
rsync: recv_generator: mkdir 
"/mnt/.software/kernel/linux-3.9-rc3/drivers/s390/scsi" failed: No space 
left on device (28)
*** Skipping any contents from this failed directory ***
.software/kernel/linux-3.9-rc3/drivers/sbus/
.software/kernel/linux-3.9-rc3/drivers/sbus/Makefile
           70 100%    0.06kB/s    0:00:01 (xfer#21399, to-check=1003/52824)
.software/kernel/linux-3.9-rc3/drivers/sbus/char/
rsync: recv_generator: mkdir 
"/mnt/.software/kernel/linux-3.9-rc3/drivers/sbus/char" failed: No space 
left on device (28)
rsync: mkstemp 
"/mnt/.software/kernel/linux-3.9-rc3/drivers/regulator/.aat2870-regulator.c.BGDwPN" 
failed: No space left on device (28)
*** Skipping any contents from this failed directory ***
.software/kernel/linux-3.9-rc3/drivers/scsi/
.software/kernel/linux-3.9-rc3/drivers/scsi/.3w-9xxx.ko.cmd
          208 100%    0.16kB/s    0:00:01 (xfer#21400, to-check=1407/53242)
.software/kernel/linux-3.9-rc3/drivers/scsi/.3w-9xxx.mod.o.cmd
        27987 100%   21.54kB/s    0:00:01 (xfer#21401, to-check=1406/53242)
.software/kernel/linux-3.9-rc3/drivers/scsi/.3w-9xxx.o.cmd
        43340 100%   32.63kB/s    0:00:01 (xfer#21402, to-check=1405/53242)
.software/kernel/linux-3.9-rc3/drivers/scsi/.3w-sas.ko.cmd
          204 100%   15.32kB/s    0:00:00 (xfer#21403, to-check=1404/53242)
.software/kernel/linux-3.9-rc3/drivers/scsi/.3w-sas.mod.o.cmd
        27975 100%    1.91MB/s    0:00:00 (xfer#21404, to-check=1403/53242)
.software/kernel/linux-3.9-rc3/drivers/scsi/.3w-sas.o.cmd
        43327 100%  983.99kB/s    0:00:00 (xfer#21405, to-check=1402/53242)
.software/kernel/linux-3.9-rc3/drivers/scsi/.3w-xxxx.ko.cmd
          208 100%    4.72kB/s    0:00:00 (xfer#21406, to-check=1401/53242)
.software/kernel/linux-3.9-rc3/drivers/scsi/.3w-xxxx.mod.o.cmd
        27987 100%  621.16kB/s    0:00:00 (xfer#21407, to-check=1400/53242)
.software/kernel/linux-3.9-rc3/drivers/scsi/.3w-xxxx.o.cmd
        43340 100%  742.53kB/s    0:00:00 (xfer#21408, to-check=1399/53242)

dmesg Output was pretty long so i posted to pastebin:
http://pastebin.com/raw.php?i=5kUS5MGA

Greets,
Stefan
--
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
Josef Bacik March 22, 2013, 8:49 p.m. UTC | #2
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
--
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
Stefan Priebe - Profihost AG March 22, 2013, 8:55 p.m. UTC | #3
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
>
--
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
diff mbox

Patch

diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
index 9ac2eca..aabaea6 100644
--- a/fs/btrfs/extent-tree.c
+++ b/fs/btrfs/extent-tree.c
@@ -4161,6 +4161,11 @@  out:
 			ret = 0;
 	}
 	if (flushing) {
+		if (ret == -ENOSPC) {
+			printk(KERN_ERR "returning enospc, dumping space info\n");
+			dump_space_info(space_info, 0, 0);
+		}
+
 		spin_lock(&space_info->lock);
 		space_info->flush = 0;
 		wake_up_all(&space_info->wait);
diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
index ca1b767..3980ae7 100644
--- a/fs/btrfs/inode.c
+++ b/fs/btrfs/inode.c
@@ -3679,11 +3679,9 @@  static struct btrfs_trans_handle *__unlink_start_trans(struct inode *dir,
 	 * 1 for the dir item
 	 * 1 for the dir index
 	 * 1 for the inode ref
-	 * 1 for the inode ref in the tree log
-	 * 2 for the dir entries in the log
 	 * 1 for the inode
 	 */
-	trans = btrfs_start_transaction(root, 8);
+	trans = btrfs_start_transaction(root, 5);
 	if (!IS_ERR(trans) || PTR_ERR(trans) != -ENOSPC)
 		return trans;
 
@@ -8127,7 +8125,7 @@  static int btrfs_rename(struct inode *old_dir, struct dentry *old_dentry,
 	 * inodes.  So 5 * 2 is 10, plus 1 for the new link, so 11 total items
 	 * should cover the worst case number of items we'll modify.
 	 */
-	trans = btrfs_start_transaction(root, 20);
+	trans = btrfs_start_transaction(root, 11);
 	if (IS_ERR(trans)) {
                 ret = PTR_ERR(trans);
                 goto out_notrans;