Placing swap partition on a loop device hangs the system

e there is some regression, or a configuration difference between the distributions? (When building 4.7-rc2, I reused config from Ubuntu 4.4 kernel.) Or if anyone already knows what the problem might be, I'm all ears. :) Best regards, James Johnston -- 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.html

RE: Recommended why to use btrfs for production?

On 06/06/2016 at 01:47, Chris Murphy wrote: > On Sun, Jun 5, 2016 at 4:45 AM, Mladen Milinkovic > wrote: > > On 06/03/2016 04:05 PM, Chris Murphy wrote: > >> Make certain the kernel command timer value is greater than the driver > >> error recovery timeout. The former is

RE: Recommended why to use btrfs for production?

On 06/05/2016 10:46 AM, Mladen Milinkovic wrote: > On 06/03/2016 04:05 PM, Chris Murphy wrote: > > Make certain the kernel command timer value is greater than the driver > > error recovery timeout. The former is found in sysfs, per block > > device, the latter can be get and set with smartctl.

RE: Compression causes kernel crashes if there are I/O or checksum errors (was: RE: kernel BUG at fs/btrfs/volumes.c:5519 when hot-removing device in RAID-1)

> I grabbed this part from the log after the machine crashed again > following trying to transfer a bunch of files that included ones with > csum errors, let me know if this looks like the same issue you were > having: > Idk? You hit a soft lockup, mine got a "kernel BUG at..." Your stack

RE: Compression causes kernel crashes if there are I/O or checksum errors (was: RE: kernel BUG at fs/btrfs/volumes.c:5519 when hot-removing device in RAID-1)

bus, which from what I read is not an uncommon failure mode. In that case, you're probably guaranteed to encounter this in short order and the system is going to go down. I did at one point awhile back test that I could boot the system degraded after it went down from hot-removing a drive.

RE: Raid 0 setup doubt.

bcache, we can put SSDs into their proper place in the memory hierarchy: Registers > L1 cache > L2 > L3 > DRAM > SSD > HDD. So conceivably the swap could be on both SSD and HDD, but you probably don't need _that_ much swap... Best regards, James Johnston -- To unsubscribe f

Compression causes kernel crashes if there are I/O or checksum errors (was: RE: kernel BUG at fs/btrfs/volumes.c:5519 when hot-removing device in RAID-1)

00 00 66 66 66 66 90 [ 13.625921] RIP [] kthread_data+0x10/0x20 [ 13.649015] RSP [ 13.653637] CR2: ffd8 [ 13.654328] ---[ end trace 90172929edc1cb9c ]--- [ 13.672040] Fixing recursive fault but reboot is needed! Best regards, James Johnston -- To unsubscribe from this list

RE: kernel BUG at fs/btrfs/volumes.c:5519 when hot-removing device in RAID-1

making the btrfs driver die very badly, but I don't know what. btrfs scrub says there are no errors... Best regards, James Johnston -- 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.html

kernel BUG at fs/btrfs/volumes.c:5519 when hot-removing device in RAID-1

00 00 00 66 66 66 66 90 [ 154.943230] RIP [] kthread_data+0x10/0x20 [ 154.944024] RSP [ 154.949641] CR2: ffd8 [ 154.950113] ---[ end trace f0effd96a236110b ]--- [ 154.950742] Fixing recursive fault but reboot is needed! Best regards, James Johnston -- To unsubscribe from