Hi Rich,
Le 18/06/2019 à 13:19, Chris Murphy a écrit :
> On Tue, Jun 18, 2019 at 4:23 PM Rich Turner wrote:
>>
>> tar: ./lib/modules/4.4.73-7-default/kernel/drivers/md/faulty.ko: Cannot
>> open: No space left on device
>
> If this really is a 4.4.73 based kernel, I expect the report is out of
>
On Tue, Jun 18, 2019 at 4:23 PM Rich Turner wrote:
>
> tar: ./lib/modules/4.4.73-7-default/kernel/drivers/md/faulty.ko: Cannot open:
> No space left on device
If this really is a 4.4.73 based kernel, I expect the report is out of
scope for this list. There have been 109 subsequent stable release
It did it again:
shrapnel share # touch test.txt
touch: cannot touch 'test.txt': No space left on device
shrapnel share # df -h
Filesystem Size Used Avail Use% Mounted on
/dev/root35G 19G 15G 56% /
devtmpfs 10M 0 10M 0% /dev
tmpfs 3.2G 1.2M 3.2G 1% /
Dmarc is off, here's the output of the allocations: it's working
correctly right now, I'll update when it does it again.
/sys/fs/btrfs/7af2e65c-3935-4e0d-aa63-9ef6be991cb9/allocation/system/flags:2
/sys/fs/btrfs/7af2e65c-3935-4e0d-aa63-9ef6be991cb9/allocation/system/raid1/used_bytes:3948544
/sys/f
On Thu, Apr 27, 2017 at 10:46 AM, Gerard Saraber wrote:
> After a reboot, I found this in the logs:
> [ 322.510152] BTRFS info (device sdm): The free space cache file
> (36114966511616) is invalid. skip it
> [ 488.702570] btrfs_printk: 847 callbacks suppressed
>
>
>
> On Thu, Apr 27, 2017 at 10:
After a reboot, I found this in the logs:
[ 322.510152] BTRFS info (device sdm): The free space cache file
(36114966511616) is invalid. skip it
[ 488.702570] btrfs_printk: 847 callbacks suppressed
On Thu, Apr 27, 2017 at 10:18 AM, Gerard Saraber wrote:
> no snapshots and no qgroups, just a st
no snapshots and no qgroups, just a straight up large volume.
shrapnel gerard-store # btrfs fi df /home/exports
Data, RAID1: total=20.93TiB, used=20.86TiB
System, RAID1: total=32.00MiB, used=3.73MiB
Metadata, RAID1: total=79.00GiB, used=61.10GiB
GlobalReserve, single: total=512.00MiB, used=544.00K
On Thu, 27 Apr 2017 08:52:30 -0500
Gerard Saraber wrote:
> I could just reboot the system and be fine for a week or so, but is
> there any way to diagnose this?
`btrfs fi df` for a start.
Also obligatory questions: do you have a lot of snapshots, and do you use
qgroups?
--
With respect,
Roman
On Tue, Aug 9, 2016 at 7:16 AM, Austin S. Hemmelgarn
wrote:
> On 2016-08-09 05:50, MegaBrutal wrote:
>>
>> 2016-06-03 14:43 GMT+02:00 Austin S. Hemmelgarn :
>>>
>>>
>>> Also, since you're on a new enough kernel, try 'lazytime' in the mount
>>> options as well, this defers all on-disk timestamp upd
On 2016-08-09 05:50, MegaBrutal wrote:
2016-06-03 14:43 GMT+02:00 Austin S. Hemmelgarn :
Also, since you're on a new enough kernel, try 'lazytime' in the mount options
as well, this defers all on-disk timestamp updates for up to 24 hours or until
the inode gets written out anyway, but keeps t
2016-06-03 14:43 GMT+02:00 Austin S. Hemmelgarn :
>
> Also, since you're on a new enough kernel, try 'lazytime' in the mount
> options as well, this defers all on-disk timestamp updates for up to 24 hours
> or until the inode gets written out anyway, but keeps the updated info in
> memory. The
On Sat, Jun 04, 2016 at 09:27:13AM +0300, Andrei Borzenkov wrote:
> 02.06.2016 15:56, Austin S. Hemmelgarn пишет:
> >
> > In your particular situation, what's happened is that you have all the
> > space allocated to chunks, but have free space within those chunks.
> > Balance never puts data in ex
02.06.2016 15:56, Austin S. Hemmelgarn пишет:
>
> In your particular situation, what's happened is that you have all the
> space allocated to chunks, but have free space within those chunks.
> Balance never puts data in existing chunks, and you can't allocate any
> new chunks, so you can't run a b
On 2016-06-02 18:45, Henk Slager wrote:
On Thu, Jun 2, 2016 at 3:55 PM, MegaBrutal wrote:
2016-06-02 0:22 GMT+02:00 Henk Slager :
What is the kernel version used?
Is the fs on a mechanical disk or SSD?
What are the mount options?
How old is the fs?
Linux 4.4.0-22-generic (Ubuntu 16.04).
Mech
On Fri, Jun 03, 2016 at 12:45:51AM +0200, Henk Slager wrote:
> The setup looks all pretty normal and btrfs should be able to handle
> it, but unfortunately your fs is a typical example that one currently
> needs to monitor/tune a btrfs fs for its 'health' in order to keep it
> running longterm.
Wh
On Thu, Jun 2, 2016 at 3:55 PM, MegaBrutal wrote:
> 2016-06-02 0:22 GMT+02:00 Henk Slager :
>> What is the kernel version used?
>> Is the fs on a mechanical disk or SSD?
>> What are the mount options?
>> How old is the fs?
>
> Linux 4.4.0-22-generic (Ubuntu 16.04).
> Mechanical disks in LVM.
> Mou
2016-06-02 0:22 GMT+02:00 Henk Slager :
> What is the kernel version used?
> Is the fs on a mechanical disk or SSD?
> What are the mount options?
> How old is the fs?
Linux 4.4.0-22-generic (Ubuntu 16.04).
Mechanical disks in LVM.
Mount: /dev/mapper/centrevg-rootlv on / type btrfs
(rw,relatime,spa
On 2016-06-01 14:30, MegaBrutal wrote:
Hi all,
I have a 20 GB file system and df says I have about 2,6 GB free space,
yet I can't do anything on the file system because I get "No space
left on device" errors. I read that balance may help to remedy the
situation, but it actually doesn't.
Some d
On Wed, Jun 1, 2016 at 11:06 PM, MegaBrutal wrote:
> Hi Peter,
>
> I tried. I either get "Done, had to relocate 0 out of 33 chunks" or
> "ERROR: error during balancing '/': No space left on device", and
> nothing changes.
>
>
> 2016-06-01 22:29 GMT+02:00 Peter Becker :
>> try this:
>>
>> btrfs fi
Hi Peter,
I tried. I either get "Done, had to relocate 0 out of 33 chunks" or
"ERROR: error during balancing '/': No space left on device", and
nothing changes.
2016-06-01 22:29 GMT+02:00 Peter Becker :
> try this:
>
> btrfs fi balance start -musage=0 /
> btrfs fi balance start -dusage=0 /
>
> b
try this:
btrfs fi balance start -musage=0 /
btrfs fi balance start -dusage=0 /
btrfs fi balance start -musage=1 /
btrfs fi balance start -dusage=1 /
btrfs fi balance start -musage=5 /
btrfs fi balance start -musage=10 /
btrfs fi balance start -musage=20 /
btrfs fi balance start -dusage=5 /
bt
Thank you too for the enlightenment. Not just now but so many times in
the past (just the compilation of your list interventions is a wiki in
its own right).
Me too, I've been meaning to create a wiki account for quite some time
(but I was partly intimidated by the formality of the request :-)
)..
George Eleftheriou posted on Mon, 07 Apr 2014 12:34:27 +0200 as excerpted:
> Browsing the btrfs wiki for a relevant warning I just found this one:
>
> Caveat: Before Linux 3.9, which adds snapshot-aware defragmentation,
> defragmenting a file which had a COW copy (either a snapshot copy or one
>
On Thu, Feb 27, 2014 at 02:16:07AM +0200, Marcus Sundman wrote:
> On 25.02.2014 22:30, Josef Bacik wrote:
> >On 02/25/2014 03:27 PM, Marcus Sundman wrote:
> >>On 25.02.2014 22:19, Hugo Mills wrote:
> >>>On Tue, Feb 25, 2014 at 01:05:51PM -0500, Jim Salter wrote:
> 370GB of 410GB used isn't real
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/26/2014 07:16 PM, Marcus Sundman wrote:
> On 25.02.2014 22:30, Josef Bacik wrote:
>> On 02/25/2014 03:27 PM, Marcus Sundman wrote:
>>> On 25.02.2014 22:19, Hugo Mills wrote:
On Tue, Feb 25, 2014 at 01:05:51PM -0500, Jim Salter wrote:
> 3
On 25.02.2014 22:30, Josef Bacik wrote:
On 02/25/2014 03:27 PM, Marcus Sundman wrote:
On 25.02.2014 22:19, Hugo Mills wrote:
On Tue, Feb 25, 2014 at 01:05:51PM -0500, Jim Salter wrote:
370GB of 410GB used isn't really "fine", it's over 90% usage.
That said, I'd be interested to know why btrfs
Josef Bacik wrote (ao):
> The -dusage= is a means to an end, so if that doesn't work try
> a larger number, up to 100. Really once you pass 50 and it's not
> working then it's time to just do a balance. The next thing is to use
> compression (too late for this option really) or add another disk.
On Tue, Feb 25, 2014 at 10:27:58PM +0200, Marcus Sundman wrote:
> On 25.02.2014 22:19, Hugo Mills wrote:
> >On Tue, Feb 25, 2014 at 01:05:51PM -0500, Jim Salter wrote:
> >>370GB of 410GB used isn't really "fine", it's over 90% usage.
> >>
> >>That said, I'd be interested to know why btrfs fi show /
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/25/2014 03:27 PM, Marcus Sundman wrote:
> On 25.02.2014 22:19, Hugo Mills wrote:
>> On Tue, Feb 25, 2014 at 01:05:51PM -0500, Jim Salter wrote:
>>> 370GB of 410GB used isn't really "fine", it's over 90% usage.
>>>
>>> That said, I'd be intereste
Try btrfs filesystem balance start -dusage=15 /home, and gradually
increase it until you see it relocate at least one chunk.
On Tue, Feb 25, 2014 at 2:27 PM, Marcus Sundman wrote:
> On 25.02.2014 22:19, Hugo Mills wrote:
>>
>> On Tue, Feb 25, 2014 at 01:05:51PM -0500, Jim Salter wrote:
>>>
>>> 37
On 25.02.2014 22:19, Hugo Mills wrote:
On Tue, Feb 25, 2014 at 01:05:51PM -0500, Jim Salter wrote:
370GB of 410GB used isn't really "fine", it's over 90% usage.
That said, I'd be interested to know why btrfs fi show /dev/sda3
shows 412.54G used, but btrfs fi df /home shows 379G used...
Thi
On Tue, Feb 25, 2014 at 01:05:51PM -0500, Jim Salter wrote:
> 370GB of 410GB used isn't really "fine", it's over 90% usage.
>
> That said, I'd be interested to know why btrfs fi show /dev/sda3
> shows 412.54G used, but btrfs fi df /home shows 379G used...
This is an FAQ...
btrfs fi show te
On 25.02.2014 20:05, Jim Salter wrote:
370GB of 410GB used isn't really "fine", it's over 90% usage.
Still, 45 gigs should be free there. If those 45 gigs aren't really
there then it shouldn't say they are there, imho.
That said, I'd be interested to know why btrfs fi show /dev/sda3 shows
4
370GB of 410GB used isn't really "fine", it's over 90% usage.
That said, I'd be interested to know why btrfs fi show /dev/sda3 shows
412.54G used, but btrfs fi df /home shows 379G used...
On 02/25/2014 11:49 AM, Marcus Sundman wrote:
Hi
I get "No space left on device" and it is unclear why
On Wed, Feb 12, 2014 at 11:45:34AM +0100, Jakob Truelsen wrote:
> Hi and thanks for the quick reply. Have remounted the filesystem with
> enospc_debug, and run the rebalance you suggested, with the trance
> below. So perhaps the next step is for me to figure out how to take a
> metadata image and s
Hi and thanks for the quick reply. Have remounted the filesystem with
enospc_debug, and run the rebalance you suggested, with the trance
below. So perhaps the next step is for me to figure out how to take a
metadata image and send it to josef (perhaps with a box of tissues)
/Jakob
[jakobt@soda ~
On 12/02/2014 09:51, Jakob Truelsen wrote:
Hello. I am experiencing "No space left on device" with a btrfs file
system, yet I cannot seem to find any exhausted resource. Could some
resource I do not know about be exhausted, or is this caused by
something else. Below is a trace of information that
On Wed, Feb 12, 2014 at 10:51:12AM +0100, Jakob Truelsen wrote:
> Hello. I am experiencing "No space left on device" with a btrfs file
> system, yet I cannot seem to find any exhausted resource. Could some
> resource I do not know about be exhausted, or is this caused by
> something else. Below is
Hugo Mills posted on Thu, 14 Nov 2013 21:00:56 + as excerpted:
>> Is there a formula to calculate how much space btrfs _might_ need?
>
> Not really. I'd expect to need something in the range 250-1500 GiB of
> headroom, depending on the size of the filesystem (and on the size of
> the metadata
On Thu, Nov 14, 2013 at 07:54:21PM +, Leonidas Spyropoulos wrote:
> Hello,
>
> I've been following this list for years and I see during various situations
> this message coming up. Some times it's a genuine problem that there is
> actually not enough space. In other cases it's some by-product
On Mon, Oct 28, 2013 at 8:05 PM, Josef Bacik wrote:
> On Sun, Oct 27, 2013 at 09:50:37AM +0100, Igor M wrote:
>> On Sun, Oct 27, 2013 at 2:00 AM, Tomasz Chmielewski wrote:
>> >> Still no messages. Parameter seems to be active as
>> >> /sys/module/printk/parameters/ignore_loglevel is Y, but there
On Mon, Oct 28, 2013 at 6:57 PM, Chris Murphy wrote:
>
> On Oct 28, 2013, at 1:40 AM, Igor M wrote:
>>
>> dmesg: http://pastebin.com/t2H1QYye
>
>
> You've got a warning related to pcie bridge on boot, with a trace that
> follows. I don't know if this could be related to some problems.
>
> [0
On Sun, Oct 27, 2013 at 09:50:37AM +0100, Igor M wrote:
> On Sun, Oct 27, 2013 at 2:00 AM, Tomasz Chmielewski wrote:
> >> Still no messages. Parameter seems to be active as
> >> /sys/module/printk/parameters/ignore_loglevel is Y, but there are no
> >> messages in log files or dmesg. Maybe I need t
On Oct 28, 2013, at 1:40 AM, Igor M wrote:
>
> dmesg: http://pastebin.com/t2H1QYye
You've got a warning related to pcie bridge on boot, with a trace that follows.
I don't know if this could be related to some problems.
[0.325976] [ cut here ]
[0.326086] WARNIN
On Mon, Oct 28, 2013 at 12:27 AM, Chris Murphy wrote:
>
> On Oct 27, 2013, at 4:46 PM, Chris Murphy wrote:
>
>>
>> On Oct 27, 2013, at 3:53 PM, Igor M wrote:
>>
>>> I made some more tests. Disk is 3TB, first cca 225GB is copied without
>>> errors.
>>> Then errors 'No space left on device' begin
On Oct 27, 2013, at 4:46 PM, Chris Murphy wrote:
>
> On Oct 27, 2013, at 3:53 PM, Igor M wrote:
>
>> I made some more tests. Disk is 3TB, first cca 225GB is copied without
>> errors.
>> Then errors 'No space left on device' begins.
>
> Post the full entire dmesg somewhere please. pastebin.c
On Oct 27, 2013, at 3:53 PM, Igor M wrote:
> I made some more tests. Disk is 3TB, first cca 225GB is copied without errors.
> Then errors 'No space left on device' begins.
Post the full entire dmesg somewhere please. pastebin.com is one option.
Chris Murphy--
To unsubscribe from this list: s
I made some more tests. Disk is 3TB, first cca 225GB is copied without errors.
Then errors 'No space left on device' begins.
Now if I use rsync with '--bwlimit' option no error occurs or if I
choose 'Retry' in Midnight Commander then continues
and after a while another error occurs and again 'Retry
On Sun, Oct 27, 2013 at 9:56 AM, Brendan Hide wrote:
> On 2013/10/27 10:50 AM, Igor M wrote:
>>
>> On Sun, Oct 27, 2013 at 2:00 AM, Tomasz Chmielewski
>> wrote:
Still no messages. Parameter seems to be active as
/sys/module/printk/parameters/ignore_loglevel is Y, but there are no
>
On 2013/10/27 10:50 AM, Igor M wrote:
On Sun, Oct 27, 2013 at 2:00 AM, Tomasz Chmielewski wrote:
Still no messages. Parameter seems to be active as
/sys/module/printk/parameters/ignore_loglevel is Y, but there are no
messages in log files or dmesg. Maybe I need to turn on some kernel
debugging
On Sun, Oct 27, 2013 at 2:00 AM, Tomasz Chmielewski wrote:
>> Still no messages. Parameter seems to be active as
>> /sys/module/printk/parameters/ignore_loglevel is Y, but there are no
>> messages in log files or dmesg. Maybe I need to turn on some kernel
>> debugging option and recompile kernel ?
> Still no messages. Parameter seems to be active as
> /sys/module/printk/parameters/ignore_loglevel is Y, but there are no
> messages in log files or dmesg. Maybe I need to turn on some kernel
> debugging option and recompile kernel ?
> Also I should mention that cca 230G+ data was copied before t
Didn't see before. btrfs progs were compiled today form git.
# btrfs version
Btrfs v0.20-rc1-358-g194aa4a
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.ht
On Sun, Oct 27, 2013 at 12:22 AM, Igor M wrote:
> On Sun, Oct 27, 2013 at 12:17 AM, Chris Murphy
> wrote:
>>
>> On Oct 26, 2013, at 3:53 PM, Igor M wrote:
>>
>>>
>>> I even added enospc_debug mount option, still no messages.
>>
>> If it were kernel enospc, you should have messages in dmesg.
>>
On Sun, Oct 27, 2013 at 12:17 AM, Chris Murphy wrote:
>
> On Oct 26, 2013, at 3:53 PM, Igor M wrote:
>
>>
>> I even added enospc_debug mount option, still no messages.
>
> If it were kernel enospc, you should have messages in dmesg.
>
> What version of btrfs progs when making the btrfs volume?
>
On Oct 26, 2013, at 3:53 PM, Igor M wrote:
>
> I even added enospc_debug mount option, still no messages.
If it were kernel enospc, you should have messages in dmesg.
What version of btrfs progs when making the btrfs volume?
>
> cp: failed to extend ‘/usr/local/mysql/data/gbdata/parts_0016
On Sat, Oct 26, 2013 at 11:35 PM, Chris Murphy wrote:
>
> On Oct 26, 2013, at 1:46 PM, Igor M wrote:
>>
>> # mount -t btrfs -o compress=lzo,compress-force=lzo /
>
> Why do you have two compression mount options? You need to pick one of these.
I removed one. I was thinking both were needed.
>
>
On Oct 26, 2013, at 1:46 PM, Igor M wrote:
>
> # mount -t btrfs -o compress=lzo,compress-force=lzo /
Why do you have two compression mount options? You need to pick one of these.
> What to do ?
Are there any kernel messages reported by dmesg at the time the copy starts and
fails? What's the
Some more info, exact error message is:
cp: writing ‘/usr/local/mysql/data/gbdata/parts_0015.MYI’: No space
left on device
cp: failed to extend ‘/usr/local/mysql/data/gbdata/parts_0015.MYI’: No
space left on device
Files are 2.7G - 7.7G big.
On Sat, Oct 26, 2013 at 9:46 PM, Igor M wrote:
> Hell
Am Samstag, 25. Mai 2013, 19:36:03 schrieb Martin Steigerwald:
> Hi!
>
> Now I got it myself what I read again and again on this mailinglist: During
> apt-get upgrade I get no space left on device.
>
> But there is:
>
> merkaba:~> df -hT /
> DateisystemTyp Größe Benutzt Verf. V
On Tue, Mar 26, 2013 at 05:28:23PM -0600, Clemens Eisserer wrote:
> Hi,
>
> I am using a btrfs loopback mounted file with lzo-compression on
> Linux-3.7.9, and I ran into "No space left on device" messages,
> although df reports only 55% of space is used:
>
> # touch testfile
> touch: cannot touc
Hi Hugo,
>> # btrfs filesystem df .
>> Data: total=28.22GB, used=14.25GB
>> System, DUP: total=8.00MB, used=12.00KB
>> System: total=4.00MB, used=0.00
>> Metadata, DUP: total=1.50GB, used=1.16GB
>
>Your metadata is close to full -- we need quite a lot of working
> space to CoW into. You (proba
On 03/27/2013 10:18 AM, Hugo Mills wrote:
On Wed, Mar 27, 2013 at 12:28:23AM +0100, Clemens Eisserer wrote:
I am using a btrfs loopback mounted file with lzo-compression on
Linux-3.7.9, and I ran into "No space left on device" messages,
although df reports only 55% of space is used:
# touch tes
On Wed, Mar 27, 2013 at 12:28:23AM +0100, Clemens Eisserer wrote:
> I am using a btrfs loopback mounted file with lzo-compression on
> Linux-3.7.9, and I ran into "No space left on device" messages,
> although df reports only 55% of space is used:
>
> # touch testfile
> touch: cannot touch `testfi
Hi again,
I wonder if this is the intended behaviour or some known issue?
Otherwise I could provide a tool written by a friend of mine which can
trigger this issue within a few minutes on a a fresh btrfs partition.
Its basically a file-system aging tester, which replays some
real-world logs taken
HI,
Am 26.03.2013 20:38, schrieb Josef Bacik:
On Tue, Mar 26, 2013 at 01:22:20PM -0600, Stefan Priebe wrote:
Hi,
but when i transfer big files i see now this one:
[20368.784736] INFO: task rsync:14911 blocked for more than 120 seconds.
[20368.821978] "echo 0 > /proc/sys/kernel/hung_task_timeout
On Tue, Mar 26, 2013 at 01:22:20PM -0600, Stefan Priebe wrote:
> Hi,
>
> but when i transfer big files i see now this one:
> [20368.784736] INFO: task rsync:14911 blocked for more than 120 seconds.
> [20368.821978] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
> disables this message.
> [203
Hi,
but when i transfer big files i see now this one:
[20368.784736] INFO: task rsync:14911 blocked for more than 120 seconds.
[20368.821978] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
[20368.895140] rsync D 8160f580 0 14911 1
0x
On Tue, Mar 26, 2013 at 01:05:36PM -0600, Stefan Priebe wrote:
> Hi Josef,
>
> Am 26.03.2013 18:45, schrieb Josef Bacik:
> >> Am 26.03.2013 16:25, schrieb Josef Bacik:
> >>> On Tue, Mar 26, 2013 at 09:03:11AM -0600, Stefan Priebe - Profihost AG
> >>> wrote:
> Hi,
> Am 26.03.2013 15:44,
Hi Josef,
Am 26.03.2013 18:45, schrieb Josef Bacik:
Am 26.03.2013 16:25, schrieb Josef Bacik:
On Tue, Mar 26, 2013 at 09:03:11AM -0600, Stefan Priebe - Profihost AG wrote:
Hi,
Am 26.03.2013 15:44, schrieb Josef Bacik:
Am 26.03.2013 13:53, schrieb Josef Bacik:
no - it's just mounted with mount
On Tue, Mar 26, 2013 at 10:19:19AM -0600, Stefan Priebe wrote:
> HI,
>
>
> Am 26.03.2013 16:25, schrieb Josef Bacik:
> > On Tue, Mar 26, 2013 at 09:03:11AM -0600, Stefan Priebe - Profihost AG
> > wrote:
> >> Hi,
> >> Am 26.03.2013 15:44, schrieb Josef Bacik:
> >> Am 26.03.2013 13:53, schrieb
HI,
Am 26.03.2013 16:25, schrieb Josef Bacik:
On Tue, Mar 26, 2013 at 09:03:11AM -0600, Stefan Priebe - Profihost AG wrote:
Hi,
Am 26.03.2013 15:44, schrieb Josef Bacik:
Am 26.03.2013 13:53, schrieb Josef Bacik:
no - it's just mounted with mount -o noatime
:~# cat /proc/mounts | grep btrfs
/
On Tue, Mar 26, 2013 at 09:03:11AM -0600, Stefan Priebe - Profihost AG wrote:
> Hi,
> Am 26.03.2013 15:44, schrieb Josef Bacik:
> Am 26.03.2013 13:53, schrieb Josef Bacik:
> no - it's just mounted with mount -o noatime
>
> :~# cat /proc/mounts | grep btrfs
> /dev/mapper/rai
Hi,
Am 26.03.2013 15:44, schrieb Josef Bacik:
Am 26.03.2013 13:53, schrieb Josef Bacik:
no - it's just mounted with mount -o noatime
:~# cat /proc/mounts | grep btrfs
/dev/mapper/raid54tb1 /mnt btrfs rw,noatime,space_cache 0 0
>>>
>>> Ok I think I see what's going on.
On Tue, Mar 26, 2013 at 07:49:16AM -0600, Stefan Priebe - Profihost AG wrote:
> Hi Josef,
>
>
> Am 26.03.2013 14:30, schrieb Josef Bacik:
> > On Tue, Mar 26, 2013 at 06:55:23AM -0600, Stefan Priebe - Profihost AG
> > wrote:
> >> Hi Josef,
> >>
> >> Am 26.03.2013 13:53, schrieb Josef Bacik:
> >>>
Hi Josef,
Am 26.03.2013 14:30, schrieb Josef Bacik:
> On Tue, Mar 26, 2013 at 06:55:23AM -0600, Stefan Priebe - Profihost AG wrote:
>> Hi Josef,
>>
>> Am 26.03.2013 13:53, schrieb Josef Bacik:
>>> On Tue, Mar 26, 2013 at 01:45:42AM -0600, Stefan Priebe wrote:
Hi,
output here:
On Tue, Mar 26, 2013 at 06:55:23AM -0600, Stefan Priebe - Profihost AG wrote:
> Hi Josef,
>
> Am 26.03.2013 13:53, schrieb Josef Bacik:
> > On Tue, Mar 26, 2013 at 01:45:42AM -0600, Stefan Priebe wrote:
> >> Hi,
> >>
> >> output here:
> >> [ 590.546162] returning enospc, space_info 3, size 0 rese
Hi Josef,
Am 26.03.2013 13:53, schrieb Josef Bacik:
> On Tue, Mar 26, 2013 at 01:45:42AM -0600, Stefan Priebe wrote:
>> Hi,
>>
>> output here:
>> [ 590.546162] returning enospc, space_info 3, size 0 reserved 0, flush
>> 2, flush_state 7 dumping space info
>> [ 590.548280] space_info 4 has 6439
On Tue, Mar 26, 2013 at 01:45:42AM -0600, Stefan Priebe wrote:
> Hi,
>
> output here:
> [ 590.546162] returning enospc, space_info 3, size 0 reserved 0, flush
> 2, flush_state 7 dumping space info
> [ 590.548280] space_info 4 has 6439292928 free, is full
> [ 590.548283] space_info total=25748
Hi,
output here:
[ 590.546162] returning enospc, space_info 3, size 0 reserved 0, flush
2, flush_state 7 dumping space info
[ 590.548280] space_info 4 has 6439292928 free, is full
[ 590.548283] space_info total=25748307968, used=19308916736, pinned=0,
reserved=32768, may_use=6438354944, re
On Fri, Mar 22, 2013 at 02:55:07PM -0600, Stefan Priebe wrote:
> Hi Jsoef,
>
> thanks!
Ok I don't think the thing I just fixed will make any difference for you so
here's another debug patch, just apply it on top of what I've already sent you
and re-run and give me the dmesg again. Thanks,
Josef
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
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 0
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 r
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?
> >>>
> >>
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 w
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 slig
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.
Greets
Hi,
Am 22.03.2013 07:41, schrieb cwillu:> On Fri, Mar 22, 2013 at 12:39 AM,
Stefan Priebe - Profihost AG
> wrote:
>> Already tried with value 5 did not help ;-( and it also happens with
>> plain cp copying a 15gb file and aborts at about 80%
>
> You tried -musage=5? Your original email said -dus
On Fri, Mar 22, 2013 at 12:39 AM, Stefan Priebe - Profihost AG
wrote:
> Already tried with value 5 did not help ;-( and it also happens with plain cp
> copying a 15gb file and aborts at about 80%
You tried -musage=5? Your original email said -dusage=5.
--
To unsubscribe from this list: send the
Already tried with value 5 did not help ;-( and it also happens with plain cp
copying a 15gb file and aborts at about 80%
Am 22.03.2013 um 07:24 schrieb cwillu :
> On Fri, Mar 22, 2013 at 12:13 AM, Roman Mamedov wrote:
>> On Thu, 21 Mar 2013 20:42:28 +0100
>> Stefan Priebe wrote:
>>
>> I migh
No this is fine it's rsync style same happens with cp.
Am 22.03.2013 um 07:13 schrieb Roman Mamedov :
> On Thu, 21 Mar 2013 20:42:28 +0100
> Stefan Priebe wrote:
>
> I might be wrong here, but doesn't this
>
>> rsync: rename
>> "/mnt/.software/kernel/linux-3.9-rc3/drivers/infiniband/hw/amso11
On Fri, Mar 22, 2013 at 12:13 AM, Roman Mamedov wrote:
> On Thu, 21 Mar 2013 20:42:28 +0100
> Stefan Priebe wrote:
>
> I might be wrong here, but doesn't this
>
>> rsync: rename
>> "/mnt/.software/kernel/linux-3.9-rc3/drivers/infiniband/hw/amso1100/""
>> ->
>> ".software/kernel/linux-3.9-rc3/driv
On Thu, 21 Mar 2013 20:42:28 +0100
Stefan Priebe wrote:
I might be wrong here, but doesn't this
> rsync: rename
> "/mnt/.software/kernel/linux-3.9-rc3/drivers/infiniband/hw/amso1100/.c2_ae.h.WEhLGP"
>
> ->
> ".software/kernel/linux-3.9-rc3/drivers/infiniband/hw/amso1100/c2_ae.h":
...try to
Should i try to downgrade?
Greets,
Stefan
Am 21.03.2013 um 20:42 schrieb Stefan Priebe :
> Yes, i've now upgraded to 3.9-rc3 same result.
>
> rsync: rename
> "/mnt/.software/kernel/linux-3.9-rc3/drivers/infiniband/hw/amso1100/.c2_ae.h.WEhLGP"
> -> ".software/kernel/linux-3.9-rc3/drivers/infin
Yes, i've now upgraded to 3.9-rc3 same result.
rsync: rename
"/mnt/.software/kernel/linux-3.9-rc3/drivers/infiniband/hw/amso1100/.c2_ae.h.WEhLGP"
->
".software/kernel/linux-3.9-rc3/drivers/infiniband/hw/amso1100/c2_ae.h":
No space left on device (28)
# btrfs filesystem df /mnt/
Data: total=
Quoting Stefan Priebe - Profihost AG (2013-03-21 14:35:59)
> Hi Chris,
>
> Am 21.03.2013 um 19:00 schrieb Chris Mason :
>
> > Quoting Stefan Priebe - Profihost AG (2013-03-21 04:03:04)
> >> Hi,
> >>
> >> while copying a 15GB file to my btrfs volume i'm getting "No space left
> >> on device".
> >
Hi Chris,
Am 21.03.2013 um 19:00 schrieb Chris Mason :
> Quoting Stefan Priebe - Profihost AG (2013-03-21 04:03:04)
>> Hi,
>>
>> while copying a 15GB file to my btrfs volume i'm getting "No space left
>> on device".
>>
>> Some information:
>>
>> # btrfs filesystem df /mnt/
>> Data: total=18.14
Quoting Stefan Priebe - Profihost AG (2013-03-21 04:03:04)
> Hi,
>
> while copying a 15GB file to my btrfs volume i'm getting "No space left
> on device".
>
> Some information:
>
> # btrfs filesystem df /mnt/
> Data: total=18.14TB, used=15.05TB
> System, DUP: total=8.00MB, used=1.94MB
> System:
On 11/02/2012 04:54 PM, Kyle Gates wrote:
So I have ended up in a state where I can't delete files with rm.
the error I get is no space on device. however I'm not even close to empty.
/dev/sdb1 38G 27G 9.5G 75%
there is about 800k files/dirs in this filesystem
extra strange is that I can in ano
1 - 100 of 128 matches
Mail list logo
