Re: [PATCH v3] lib: add size unit t/p/e to memparse

2014-06-13 Thread Brendan Hide
On 12/06/14 23:15, Andrew Morton wrote: On Wed, 2 Apr 2014 16:54:37 +0800 Gui Hecheng guihc.f...@cn.fujitsu.com wrote: For modern filesystems such as btrfs, t/p/e size level operations are common. add size unit t/p/e parsing to memparse Signed-off-by: Gui Hecheng guihc.f...@cn.fujitsu.com ---

Re: [PATCH v4] lib: add size unit t/p/e to memparse

2014-06-13 Thread Brendan Hide
On 13/06/14 03:42, Gui Hecheng wrote: For modern filesystems such as btrfs, t/p/e size level operations are common. add size unit t/p/e parsing to memparse Signed-off-by: Gui Hecheng guihc.f...@cn.fujitsu.com --- changelog v1-v2: replace kilobyte with kibibyte, and others v2-v3:

Re: [PATCH v4] lib: add size unit t/p/e to memparse

2014-06-13 Thread Gui Hecheng
On Fri, 2014-06-13 at 07:55 +0200, Brendan Hide wrote: On 13/06/14 03:42, Gui Hecheng wrote: For modern filesystems such as btrfs, t/p/e size level operations are common. add size unit t/p/e parsing to memparse Signed-off-by: Gui Hecheng guihc.f...@cn.fujitsu.com --- changelog

Re: Deadlock/high load

2014-06-13 Thread Alin Dobre
On 13/06/14 04:37, Liu Bo wrote: The output of 'btrfs filesystem df' is appreciate, it can help determine if the FS has entered into 'almost full' situation, and that may cause a bug that pages are not marked with writeback tag and lead to processes's endless waiting. I'll send it as soon

Re: Deadlock/high load

2014-06-13 Thread Alin Dobre
On 13/06/14 04:37, Liu Bo wrote: The output of 'btrfs filesystem df' is appreciate, it can help determine if the FS has entered into 'almost full' situation, and that may cause a bug that pages are not marked with writeback tag and lead to processes's endless waiting. The output now (when

Re: [PATCH v3] lib: add size unit t/p/e to memparse

2014-06-13 Thread Hugo Mills
On Fri, Jun 13, 2014 at 07:54:44AM +0200, Brendan Hide wrote: On 12/06/14 23:15, Andrew Morton wrote: On Wed, 2 Apr 2014 16:54:37 +0800 Gui Hecheng guihc.f...@cn.fujitsu.com wrote: + * %K (for kibibytes, or 1024 bytes), + * %M (for mebibytes, or 1048576 bytes), + * %G (for gibibytes, or

Re: [PATCH v2] Btrfs: fix RCU correctness warning when running sanity tests

2014-06-13 Thread Filipe David Manana
On Tue, Jun 10, 2014 at 7:17 PM, Filipe David Borba Manana fdman...@gmail.com wrote: When CONFIG_PROVE_RCU=y and CONFIG_PROVE_RCU_REPEATEDLY=y, the following was dumped in dmesg: [ 3197.218064] === [ 3197.218064] [ INFO: suspicious RCU usage. ] [ 3197.218066]

Btrfs filesystem read only on error

2014-06-13 Thread David Bloquel
Hi, Today my btrfs disk suddently turned to read only after than an error occured, I guess it's a security measure to avoid any corrupted data after a filesystem error. Here is the syslog: Jun 13 04:59:39 nas1 kernel: [110663.709572] btrfs: page allocation failure: order:1, mode:0x200020 Jun 13

[GIT PULL] Btrfs #2 for 3.16

2014-06-13 Thread Chris Mason
Hi Linus, Please pull my for-linus branch: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus This has a few fixes since our last pull and a new ioctl for doing btree searches from userland. It's very similar to the existing ioctl, but lets us return larger items

Re: [PATCH 2/2] Remove a leading '+'.

2014-06-13 Thread Eric Sandeen
On 6/13/14, 4:34 PM, Adam Buchbinder wrote: It was added in commit aab7f3ae3eb02fb7e8a6a31d7e2ada704a3dcd5e, most likely as a copy-pasteo. Signed-off-by: Adam Buchbinder abuchbin...@google.com --- btrfs-show-super.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: R: Re: Slow startup of systemd-journal on BTRFS

2014-06-13 Thread Goffredo Baroncelli
Hi Dave On 06/13/2014 01:24 AM, Dave Chinner wrote: On Thu, Jun 12, 2014 at 12:37:13PM +, Duncan wrote: Goffredo Baroncelli kreij...@libero.it posted on Thu, 12 Jun 2014 13:13:26 +0200 as excerpted: systemd has a very stupid journal write pattern. It checks if there is space in the file

[PATCH] Fix a use-after-free in the volumes code.

2014-06-13 Thread Adam Buchbinder
When a struct btrfs_fs_devices was being torn down by btrfs_close_devices(), there was an invalidated pointer in the global list fs_uuids which still pointed to it; if a device was closed and then reopened (which btrfs-convert does), freed memory would be accessed. This was found using

Re: [PATCH] Properly size the leafsize field in the mdrestore_struct struct.

2014-06-13 Thread Adam Buchbinder
I'd like to follow up on this a bit, because the way I found it was *weird*. MSan found an uninitialized write. Reproducing the issue through GDB showed that there's a struct mdrestore_struct type with a member of type u64 called 'leafsize' which was... half-initialized? Four bytes were

Re: some project ideas: NFS4 ACLs, resilience on the same device, allowing to specify which devices are distinct in a RAID

2014-06-13 Thread Christoph Anton Mitterer
On Sat, 2014-06-07 at 10:25 +0200, Goffredo Baroncelli wrote: You can add new ideas to the wiki pages, supporting by link and other info were available. This is the real nature of the wiki pages. I've added some stuff now:

Re: Slow startup of systemd-journal on BTRFS

2014-06-13 Thread Duncan
Goffredo Baroncelli posted on Sat, 14 Jun 2014 00:19:31 +0200 as excerpted: On 06/13/2014 01:24 AM, Dave Chinner wrote: On Thu, Jun 12, 2014 at 12:37:13PM +, Duncan wrote: FWIW, either 4 byte or 8 MiB fallocate calls would be bad, I think actually pretty much equally bad without NOCOW

Re: Btrfs filesystem read only on error

2014-06-13 Thread Duncan
David Bloquel posted on Fri, 13 Jun 2014 12:51:32 +0200 as excerpted: Informations about my system: Linux nas1 3.12-0.bpo.1-amd64 #1 SMP Debian 3.12.9-1~bpo70+1 (2014-02-07) x86_64 GNU/Linux brtfs version: Btrfs v0.19 Yikes, that's old! Particularly the 0.19 btrfs-progs, tho there have