I tried the same routine on 32GB usb sticks. Same exact problems. 32GB
seems a bit much for a --mixed btrfs.
I haven't tried ssd_spread, maybe it's beneficial. However, as I wrote
above, disabling autodefrag gets rid completely of the INFO: hung
task messages but even though the kernel doesn't
On Wed, Sep 03, 2014 at 08:03:51AM +0200, john terragon wrote:
I tried the same routine on 32GB usb sticks. Same exact problems. 32GB
seems a bit much for a --mixed btrfs.
I haven't tried ssd_spread, maybe it's beneficial. However, as I wrote
above, disabling autodefrag gets rid completely of
On 09/02/2014 09:31 PM, john terragon wrote:
Rsync finished. FWIW in the end it reported an average speed of about
900K/sec. Without autodefrag there have been no messages about hung
kworkers even though rsync seemingly keeps getting hung for several
minutes throughout the whole execution.
I wasn't sure what you meant with wherever you mkfs btrfs so I dd'd
all the three possible cases:
1) here's the dmcrypt device on which I mkfs.btrfs
2097152000 bytes (2.1 GB) copied, 487.265 s, 4.3 MB/s
2) here's the partition of the usb stick (which has another partition
containing /boot)
On Sep 3, 2014, at 8:11 AM, john terragon jterra...@gmail.com wrote:
It's a usb2 device but doesn't it seem kind of slow?
Not atypical, I have one that's the same, and another that's ~21MB/s, both are
USB 2.
[Certain older Apple Mac firmware boot faster with the slow stick than the fast
I will definitely try the latest 3.14.x (never had any problem of this
kind with it). And I'll look into the other possibilities you pointed
out. However what I can tell you right now is this:
-the filesystem was new. I've been bitten by this bug with 3.15 and
3.16 and I kept
trying to do the
john terragon posted on Tue, 02 Sep 2014 08:12:36 +0200 as excerpted:
I will definitely try the latest 3.14.x (never had any problem of this
kind with it). And I'll look into the other possibilities you pointed
out. However what I can tell you right now is this:
-the filesystem was new.
Nice...now I get the hung task even with 3.14.17 And I tried with
4K for node and leaf size...same result. And to top it all off, today
I've been bitten by the bug also on my main root fs (which is on two
fast ssd), although with 3.16.1.
Is it at least safe for the data? I mean, as long as
On 09/02/2014 03:56 PM, john terragon wrote:
Nice...now I get the hung task even with 3.14.17 And I tried with
4K for node and leaf size...same result. And to top it all off, today
I've been bitten by the bug also on my main root fs (which is on two
fast ssd), although with 3.16.1.
Is
I don't know what to tell you about the ENOSPC code being heavily
involved. At this point I'm using this simple test to see if things
improve:
-freshly created btrfs on dmcrypt,
-rsync some stuff (since the fs is empty I could just use cp but I
keep the test the same as it was when I had the
OK, so I'm using 3.17-rc3, same test on a flash usb drive, no
autodefrag. The situation is even stranger. The rsync is clearly
stuck, it's trying to write the same file for much more than 120 secs.
However dmesg is clean, no INFO: task kworker/u16:11:1763 blocked for
more than 120 seconds or
Rsync finished. FWIW in the end it reported an average speed of about
900K/sec. Without autodefrag there have been no messages about hung
kworkers even though rsync seemingly keeps getting hung for several
minutes throughout the whole execution.
Thanks
John
On Tue, Sep 2, 2014 at 10:48 PM,
On Sep 2, 2014, at 12:40 AM, Duncan 1i5t5.dun...@cox.net wrote:
Mkfs.btrfs used to default to 4 KiB node/leaf sizes; now days it defaults
to 16 KiB as that's far better for most usage. I wonder if USB sticks
are an exception…
USB sticks 1 GB get 16KB nodesize also. At = 1 GB, mixed-bg
On Tue, Sep 02, 2014 at 05:20:29AM +, Duncan wrote:
suspect your firmware is SERIOUSLY out of space and shuffling, as that'll
slow the balance down too, and again after), try running fstrim on the
device. It may or may not work on that device, but if it does and the
firmware /was/ out
Chris Murphy posted on Tue, 02 Sep 2014 20:44:06 -0600 as excerpted:
On Sep 2, 2014, at 12:40 AM, Duncan 1i5t5.dun...@cox.net wrote:
Mkfs.btrfs used to default to 4 KiB node/leaf sizes; now days it
defaults to 16 KiB as that's far better for most usage. I wonder if
USB sticks are an
Hi.
I'm not sure if this is related to the hung task problem that I've
been seeing in this ml for a while. But I've been having this
seemingly related problem with 3.15, 3.16 and now 3.17-rc3 (which, if
I'm not mistaken, should have a fix for the hung task problem). So
here it is: I have a usb
On 09/01/2014 09:33 AM, john terragon wrote:
Hi.
I'm not sure if this is related to the hung task problem that I've
been seeing in this ml for a while. But I've been having this
seemingly related problem with 3.15, 3.16 and now 3.17-rc3 (which, if
I'm not mistaken, should have a fix for
I was trying it again and it seems to have completed, albeit very
slowly (even for an usb flash drive). Was the 3.14 series the last
immune one from this problem? Should I try the latest 3.14.x?
Thanks
John
On Mon, Sep 1, 2014 at 6:02 PM, Chris Mason c...@fb.com wrote:
On 09/01/2014 09:33 AM,
john terragon posted on Mon, 01 Sep 2014 18:36:49 +0200 as excerpted:
I was trying it again and it seems to have completed, albeit very slowly
(even for an usb flash drive). Was the 3.14 series the last immune one
from this problem? Should I try the latest 3.14.x?
The 3.14 series was before
19 matches
Mail list logo