The return values of btrfs_item_offset_nr and btrfs_item_size_nr are of
type u32. To avoid mixing signed and unsigned integers we should also
declare dsize and last_off to be of type u32.
Signed-off-by: Alexandru Moise <00moses.alexande...@gmail.com>
---
fs/btrfs/ctree.c | 4 ++--
1 file changed,
Am Fri, 14 Aug 2015 23:37:37 +0200
schrieb Marc Joliet :
> If I notice anything amiss, I'll report back.
I haven't noticed anything amiss, so I'm marking this thread as SOLVED.
--
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustr
At initializing time, for threshold-able workqueue, it's max_active
of kernel workqueue should be 1 and grow if it hits threshold.
But due to the bad naming, there is both 'max_active' for kernel
workqueue and btrfs workqueue.
So wrong value is given at workqueue initialization.
This patch fixes
Marc MERLIN wrote on 2015/08/22 07:37 -0700:
On Mon, Aug 17, 2015 at 07:49:04AM -0700, Marc MERLIN wrote:
On Mon, Aug 17, 2015 at 10:01:16AM +0800, Qu Wenruo wrote:
Hi Marc,
Hi Qu, thanks for your answer and looking at this.
Did btrfs-debug-tree also has the crash?
If not, would you plea
Stefan,
Please send your patches to the mailing list for reviews by everybody.
Do you see any patch below which wasn't posted to the mailing list. ?
Thanks, Anand
Qu Wenruo (1):
btrfs: async_thread: Fix workqueue 'max_active' value when
initializing
Tsutomu Itoh (1):
Btrfs:
I'm trying out RAID5 to understand its space usage. First off, I've 3
devices of 2GB each, in RAID5. Old school RAID5 tells me I've 4GB of
usable space. Actual fact: I've about 3.5GB, until it tells me I'm out
of space. This is understandable, as Metadata and System took up some
space.
Next, I tri
On Mon, Aug 24, 2015 at 09:10:30AM +0800, Qu Wenruo wrote:
> Would you please take the following output?
>
> 1) btrfs check output
> With error message if it happens.
myth:~# btrfs check /dev/mapper/crypt_sdd1
Checking filesystem on /dev/mapper/crypt_sdd1
UUID: 024ba4d0-dacb-438d-9f1b-eeb34083fe
Marc MERLIN wrote on 2015/08/23 21:28 -0700:
On Mon, Aug 24, 2015 at 09:10:30AM +0800, Qu Wenruo wrote:
Would you please take the following output?
1) btrfs check output
With error message if it happens.
myth:~# btrfs check /dev/mapper/crypt_sdd1
Checking filesystem on /dev/mapper/crypt_sdd
