Re: Btrfs progs pre-release 4.3-rc1

On Mon, Nov 2, 2015 at 4:14 PM, David Sterba wrote: > Hi, > > the kernel 4.3 was released yesterday, the btrfs-progs will follow at the end > of this week. I've tagged an rc1 from current devel branch. There are a lots > of > small invisible changes and one change in the

mkfs.btrfs doesn't detect SSD

Hey. I'm creating a filesystem on Samsung Evo 850 Pro on top of a dm- crypt/LUKS container (with TRIM not being passed on, for the usual security reasons): # mkfs.btrfs --label system /dev/mapper/system btrfs-progs v4.2.2 See http://btrfs.wiki.kernel.org for more information. Label: 

Re: [PATCH] btrfs: qgroup: fix quota disable during rescan

On Fri, Nov 6, 2015 at 6:36 PM, Justin Maggard wrote: > There's a race condition that leads to a NULL pointer dereference if you > disable quotas while a quota rescan is running. To fix this, we just need > to wait for the quota rescan worker to actually exit before tearing

Re: [PATCH] btrfs: test quota disable during quota rescan

On Fri, Nov 6, 2015 at 6:40 PM, Justin Maggard wrote: > This test case tests if we are able to disable quotas on a filesystem > while a quota rescan is running. Up to now (4.3) this would result > in a kernel NULL pointer dereference. > > Fixed by patch (btrfs: qgroup: fix

Re: mkfs.btrfs doesn't detect SSD

On Sat, Nov 7, 2015 at 4:05 PM, Christoph Anton Mitterer wrote: > Hey. > > I'm creating a filesystem on Samsung Evo 850 Pro on top of a dm- > crypt/LUKS container (with TRIM not being passed on, for the usual > security reasons): > # mkfs.btrfs --label system

Re: mkfs.btrfs doesn't detect SSD

Hmm in fact it seems to be the kernel who wrongly, detects the type: /sys/block/sdb/queue/rotational = 1 or more like the USB/SATA bridge simply reports it wrong. Anyway, is there a way to override? Or will setting /sys/block/sdb/queue/rotational = 0 give the expected behaviour? Thanks, Chris.

Reproducible corruption issue in stable, with possible patch unmerged?

[repost, since the previous mail was rejected by vger.kernel.org] I got these messages in my dmesg: [ 2587.841376] BTRFS error (device sdc1): partial page write in btrfs with offset 0 and length 8392704 [ 2588.814182] BTRFS critical (device sdc1): bad ordered accounting left 0 size 4096 With no

Process is blocked for more than 120 seconds

Hi everyone, I have noticed the following in the log. The system continues to run, but I am not sure for how long it will be stable. Should I start worrying? Thanks in advance for the opinion. # uname -a Linux Debian 4.2.3-2~bpo8+1 (2015-10-20) i686 GNU/Linux # mount | grep /var /dev/sdd2 on

Re: Btrfs progs pre-release 4.3-rc1

David Sterba posted on Fri, 06 Nov 2015 11:53:53 +0100 as excerpted: > On Tue, Nov 03, 2015 at 12:10:14AM +, Duncan wrote: >> David Sterba posted on Mon, 02 Nov 2015 16:14:53 +0100 as excerpted: >> >> > the kernel 4.3 was released yesterday, the btrfs-progs will follow at >> > the end of

Re: boot from snapshot and take snapshot from here.

On Sat, Nov 07, 2015 at 08:04:01PM +0100, Jakob Schürz wrote: > Hi there! > > I can't find any Information for my Problem. And I try to explain, what > I want. [snip] > BUT > > When i boot from f.e. @debian-snap2, the mechanics doesn't work any longer. > > btrfs subvol snapshot @debian-snap2

Re: boot from snapshot and take snapshot from here.

Am 2015-11-07 um 20:18 schrieb Hugo Mills: > On Sat, Nov 07, 2015 at 08:04:01PM +0100, Jakob Schürz wrote: >> Hi there! >> >> I can't find any Information for my Problem. And I try to explain, what >> I want. > [snip] >> BUT >> >> When i boot from f.e. @debian-snap2, the mechanics doesn't work any

Re: Reproducible corruption issue in stable, with possible patch unmerged?

On Sat, Nov 07, 2015 at 04:36:56PM +0100, Diego Call. wrote: > [repost, since the previous mail was rejected by vger.kernel.org] > > I got these messages in my dmesg: > > [ 2587.841376] BTRFS error (device sdc1): partial page write in btrfs > with offset 0 and length 8392704 > [ 2588.814182]

cannot mount btrfs volume read/write (+task blocked backtrace)

Hi all, I am trying to mount a btrfs filesystem, and I have been told on freenode/#btrfs to try the mailing list for more precise advice. My setup is as follow : one debian server (stretch, 4.2.0-1-amd64 #1 SMP Debian 4.2.3-2 (2015-10-14) x86_64) with 5 disks running in a btrfs raid6 volume.

Re: [PATCH] btrfs: clear bio reference after submit_one_bio()

Hi Holger, I think it will cause an invalid paging request, just like in case that Naohiro has fixed. I am not running the "latest and greatest" btrfs in my system, and it is not easy to set it up, that's why I cannot submit patches based on the latest code, I can only review and comment on

boot from snapshot and take snapshot from here.

Hi there! I can't find any Information for my Problem. And I try to explain, what I want. There is a btrfs-partition on my laptop. I take snapshots every hour from the subvolume @debian. btrfs subvol snapshot @debian @debian-snap1 Then I transfer this snapshot to my external HD btrfs send

strange "No space left on device"

Hey. I just repeatedly did the following twice on a ~8GB USB stick, under Debian sid (ergo kernel 4.2.0-1-amd64, btrfsprogs 4.2.2-1). First, created some GPT on the stick: Number  Start (sector)End (sector)  Size   Code  Name    12048 1048575   511.0 MiB   EF02  BIOS

Re: strange "No space left on device"

On Sat, 2015-11-07 at 23:30 +, Hugo Mills wrote: >    These are all really small. Well enough for booting =) >    I would suggest running mkfs with --mixed for all of these > filesystems and trying again. I thought btrfs would do that automatically:

Re: strange "No space left on device"

On Sun, Nov 08, 2015 at 12:22:42AM +0100, Christoph Anton Mitterer wrote: > Hey. > > I just repeatedly did the following twice on a ~8GB USB stick, under > Debian sid (ergo kernel 4.2.0-1-amd64, btrfsprogs 4.2.2-1). > > First, created some GPT on the stick: > Number  Start (sector)End

Re: cannot mount btrfs volume read/write (+task blocked backtrace)

After 8 hours, "btrfs check --readonly" is still "checking quota groups". It does not have any IO activity, but uses 100% CPU. #top 1143 root 20 0 2266596 2.148g 1124 R 100.0 56.0 183:37.14 btrfs check --readonly /dev/sda1