On 2017年10月04日 12:00, Asif Youssuff wrote:
Thanks for the advice.
On 10/03/2017 09:38 PM, Qu Wenruo wrote:
[210017.281912] BTRFS info (device sdb): disk space caching is enabled
[210017.281915] BTRFS info (device sdb): has skinny extents
[210017.402084] BTRFS error (device sdb): super_tota
Any suggestions on this? Or do I just blow it away and hope the bug is
fixed in a newer version?
Regards
Tim
On Mon, Oct 2, 2017 at 8:44 PM, Timothy White wrote:
> I have a BTRFS RAID 10 filesystem that was crashing and going into RO
> mode. A did a kernel upgrade, upgraded btrfs tools to the l
Thanks for the advice.
On 10/03/2017 09:38 PM, Qu Wenruo wrote:
[210017.281912] BTRFS info (device sdb): disk space caching is enabled
[210017.281915] BTRFS info (device sdb): has skinny extents
[210017.402084] BTRFS error (device sdb): super_total_bytes
92017859088384
mismatch with fs_devi
Because the values of BTRFS_FS_EXCL_OP and BTRFS_FS_QUOTA_OVERRIDE overlap,
we should change the value.
First, BTRFS_FS_EXCL_OP was set to 14.
commit 171938e52807 ("btrfs: track exclusive filesystem operation in flags")
Next, the value of BTRFS_FS_QUOTA_OVERRIDE was set to 14.
commit f29efe
On 2017年10月04日 07:32, Asif Youssuff wrote:
Hi,
My power went out at my home, and I'm now having trouble mounting my array.
I'm mounting with the 'recovery' option in fstab.
When mounting, dmesg output shows:
[210017.281912] BTRFS info (device sdb): disk space caching is enabled
[210017.2819
Hi,
We are researchers from UT Austin, working on building CrashMonkey[1], a
simple, flexible, file-system agnostic test framework to
systematically check file-systems for inconsistencies if a failure
occurs during a file operation.
Here is a brief description of what we are trying to do:
Firstl
Hi,
My power went out at my home, and I'm now having trouble mounting my array.
I'm mounting with the 'recovery' option in fstab.
When mounting, dmesg output shows:
[210017.281912] BTRFS info (device sdb): disk space caching is enabled
[210017.281915] BTRFS info (device sdb): has skinny extent
On 10/3/2017 2:11 PM, Hugo Mills wrote:
Hi, Stephen,
On Tue, Oct 03, 2017 at 08:52:04PM +, Stephen Nesbitt wrote:
Here it i. There are a couple of out-of-order entries beginning at 117. And
yes I did uncover a bad stick of RAM:
btrfs-progs v4.9.1
leaf 2589782867968 items 134 free spac
On Tue, Oct 03, 2017 at 01:40:51PM -0700, Matthew Wilcox wrote:
> On Wed, Oct 04, 2017 at 07:10:35AM +1100, Dave Chinner wrote:
> > On Tue, Oct 03, 2017 at 03:19:18PM +0200, Martin Steigerwald wrote:
> > > [repost. I didn´t notice autocompletion gave me wrong address for
> > > fsdevel,
> > > blac
Hi, Stephen,
On Tue, Oct 03, 2017 at 08:52:04PM +, Stephen Nesbitt wrote:
> Here it i. There are a couple of out-of-order entries beginning at 117. And
> yes I did uncover a bad stick of RAM:
>
> btrfs-progs v4.9.1
> leaf 2589782867968 items 134 free space 6753 generation 3351574 owner 2
>
On Wed, Oct 04, 2017 at 07:10:35AM +1100, Dave Chinner wrote:
> On Tue, Oct 03, 2017 at 03:19:18PM +0200, Martin Steigerwald wrote:
> > [repost. I didn´t notice autocompletion gave me wrong address for fsdevel,
> > blacklisted now]
> >
> > Hello.
> >
> > What do you think of
> >
> > http://open
On 10/03/17 13:10, Dave Chinner wrote:
> On Tue, Oct 03, 2017 at 03:19:18PM +0200, Martin Steigerwald wrote:
>> [repost. I didn´t notice autocompletion gave me wrong address for fsdevel,
>> blacklisted now]
>>
>> Hello.
>>
>> What do you think of
>>
>> http://open-zfs.org/wiki/Projects/ZFS_Channel
On Tue, Oct 03, 2017 at 03:19:18PM +0200, Martin Steigerwald wrote:
> [repost. I didn´t notice autocompletion gave me wrong address for fsdevel,
> blacklisted now]
>
> Hello.
>
> What do you think of
>
> http://open-zfs.org/wiki/Projects/ZFS_Channel_Programs
Domain not found.
-Dave.
--
Dave
On Tue, Oct 03, 2017 at 01:06:50PM -0700, Stephen Nesbitt wrote:
> All:
>
> I came back to my computer yesterday to find my filesystem in read
> only mode. Running a btrfs scrub start -dB aborts as follows:
>
> btrfs scrub start -dB /mnt
> ERROR: scrubbing /mnt failed for device id 4: ret=-1, err
All:
I came back to my computer yesterday to find my filesystem in read only
mode. Running a btrfs scrub start -dB aborts as follows:
btrfs scrub start -dB /mnt
ERROR: scrubbing /mnt failed for device id 4: ret=-1, errno=5
(Input/output error)
ERROR: scrubbing /mnt failed for device id 5: ret
From: Goffredo Baroncelli
Jean-Denis Girard noticed commit c821e7f3 "pass bytes to
btrfs_bio_alloc" (https://patchwork.kernel.org/patch/9763081/) introduces a
regression on 32 bit machines.
When CONFIG_LBDAF is _not_ defined (CONFIG_LBDAF == Support for large
(2TB+) block devices and files) secto
On Tue, Oct 03, 2017 at 03:47:26PM +0900, Misono, Tomohiro wrote:
> kernel 4.14 introduces new function for checking if all chunks is ok for
> mount with -o degraded option.
>
> commit 21634a19f646 ("btrfs: Introduce a function to check if all
> chunks a OK for degraded rw mount")
>
> As a re
On Mon, Oct 02, 2017 at 05:34:12PM +0900, Tsutomu Itoh wrote:
> Because the values of BTRFS_FS_QUOTA_OVERRIDE and BTRFS_FS_EXCL_OP overlap,
> we should change the value.
>
> Signed-off-by: Tsutomu Itoh
Please write a more descriptive subject and changelog.
> ---
> fs/btrfs/ctree.h | 3 +--
> 1
From: Anand Jain
Write and flush errors are critical errors, upon which the device fd
must be closed and marked as failed.
There are two type of device close in btrfs, one, close as part
of clean up where we shall release the struct btrfs_device and
or btrfs_fs_devices as well. And the other typ
From: Anand Jain
This patch provides helper functions to force a device to failed,
and we need it for the following reasons,
1) a. It can be reported that device has failed when it does and
b. Close the device when it goes offline so that blocklayer can
cleanup
2) Identify the candidate
When one device fails it has to be closed and marked as failed.
Further it needs sysfs (or some) interface to provide complete
information about the device and the volume status to the user
land from the kernel. Next when the disappeared device reappears
we need to resilver/insync depending on the
On Tue, Oct 03, 2017 at 05:45:54PM +0200, fred.lar...@free.fr wrote:
> Hi,
>
>
> > What does "btrfs sub list -a /RAID01/" say?
> Nothing (no lines displayed)
>
> > Also "grep /RAID01/ /proc/self/mountinfo"?
> Nothing (no lines displayed)
>
>
> Also server has been rebooted many times and n
Hi,
> What does "btrfs sub list -a /RAID01/" say?
Nothing (no lines displayed)
> Also "grep /RAID01/ /proc/self/mountinfo"?
Nothing (no lines displayed)
Also server has been rebooted many times and no process has left "deleted open
files" on the volume (lsof...).
Fred.
- Mail orig
Remove dead assigment of num_bytes
Also as num_bytes only used in will_compress block as
copy of total_in just replace that with total_in and drop num_bytes entire
Signed-off-by: Timofey Titovets
Reviewed-by: Nikolay Borisov
---
fs/btrfs/inode.c | 10 +++---
1 file changed, 3 insertions(+)
At now btrfs_dedupe_file_range() restricted to 16MiB range for
limit locking time and memory requirement for dedup ioctl()
For too big input rage code silently set range to 16MiB
Let's remove that restriction by do iterating over dedup range.
That's backward compatible and will not change anythin
At now while switch page bits in data ranges
we always hande +1 page, for cover case
where end of data range is not page aligned
Let's handle that case more obvious and efficient
Check end aligment directly and touch +1 page
only then needed
Signed-off-by: Timofey Titovets
---
fs/btrfs/extent_i
We need to call extent_range_clear_dirty_for_io()
on compression range to prevent application from changing
page content, while pages compressing.
but "(end - start)" can be much (up to 1024 times) bigger
then compression range (BTRFS_MAX_UNCOMPRESSED), so optimize that
by calculating compression
Some patches has review, some not, all compile tested and hand tested.
(i.e. boot into patched system and do some small tests).
All based on kDave for-next branch
Patches:
1. Just remove useless u64 num_bytes from compress_file_range()
No functional changes
2. For make compression on on mmap'd
Hi,
It seems to me that the proposal[1] for a snapshot-aware defrag has long
been abandoned. Since most peoples badly need this feature I tought about
how to possibly speed up the achievement of this goal.
I know of several bounty-based kickstarting platforms, among them the best
ones are pro
[repost. I didn´t notice autocompletion gave me wrong address for fsdevel,
blacklisted now]
Hello.
What do you think of
http://open-zfs.org/wiki/Projects/ZFS_Channel_Programs
?
There are quite some BTRFS maintenance programs like the deduplication stuff.
Also regular scrubs… and in certain c
On Tue, 3 Oct 2017 10:54:05 +
Hugo Mills wrote:
>There are other possibilities for missing space, but let's cover
> the obvious ones first.
One more obvious thing would be files that are deleted, but still kept open by
some app (possibly even from network, via NFS or SMB!). @Frederic, di
2017-10-03 13:54 GMT+03:00 Hugo Mills :
> On Tue, Oct 03, 2017 at 12:44:29PM +0200, btrfs.fr...@xoxy.net wrote:
>> Hi,
>>
>> I can't figure out were 3TB on a 36 TB BTRFS volume (on LVM) are gone !
>>
>> I know BTRFS can be tricky when speaking about space usage when using many
>> physical drives i
On Tue, Oct 03, 2017 at 12:44:29PM +0200, btrfs.fr...@xoxy.net wrote:
> Hi,
>
> I can't figure out were 3TB on a 36 TB BTRFS volume (on LVM) are gone !
>
> I know BTRFS can be tricky when speaking about space usage when using many
> physical drives in a RAID setup, but my conf is a very simple B
Hi,
I can't figure out were 3TB on a 36 TB BTRFS volume (on LVM) are gone !
I know BTRFS can be tricky when speaking about space usage when using many
physical drives in a RAID setup, but my conf is a very simple BTRFS volume
without RAID(single Data type) using the whole disk (perhaps did I do
Hello.
What do you think of
http://open-zfs.org/wiki/Projects/ZFS_Channel_Programs
?
There are quite some BTRFS maintenance programs like the deduplication stuff.
Also regular scrubs… and in certain circumstances probably balances can make
sense.
In addition to this XFS got scrub functionali
This patch updates help/document of "btrfs device remove" in two points:
1. Add explanation of 'missing' for 'device remove'. This is only
written in wikipage currently.
(https://btrfs.wiki.kernel.org/index.php/Using_Btrfs_with_Multiple_Devices)
2. Add example of device removal in the man documen
36 matches
Mail list logo