Re: updatedb does not index /home when /home is Btrfs

2017-11-04 Thread Nicholas D Steeves
On 4 November 2017 at 14:55, Chris Murphy wrote: > On Sat, Nov 4, 2017 at 12:27 PM, Andrei Borzenkov wrote: >> 04.11.2017 10:05, Adam Borowski пишет: >>> On Sat, Nov 04, 2017 at 09:26:36AM +0300, Andrei Borzenkov wrote: 04.11.2017 07:49, Adam

btrfs-progs: check --repair crashes with BUG ON

2017-11-04 Thread Stefan Priebe - Profihost AG
Hello, after a power failure i have a btrfs volume which isn't mountable. dmesg shows: parent transid verify failed on 181846016 wanted 143404 found 143399 If i run: btrfs check --repair /dev/mapper/crypt_md1 The output is: parent transid verify failed on 181846016 wanted 143404 found 143399

Re: updatedb does not index /home when /home is Btrfs

2017-11-04 Thread Chris Murphy
On Sat, Nov 4, 2017 at 12:27 PM, Andrei Borzenkov wrote: > 04.11.2017 10:05, Adam Borowski пишет: >> On Sat, Nov 04, 2017 at 09:26:36AM +0300, Andrei Borzenkov wrote: >>> 04.11.2017 07:49, Adam Borowski пишет: On Fri, Nov 03, 2017 at 06:15:53PM -0600, Chris Murphy wrote:

Re: updatedb does not index /home when /home is Btrfs

2017-11-04 Thread Andrei Borzenkov
04.11.2017 10:05, Adam Borowski пишет: > On Sat, Nov 04, 2017 at 09:26:36AM +0300, Andrei Borzenkov wrote: >> 04.11.2017 07:49, Adam Borowski пишет: >>> On Fri, Nov 03, 2017 at 06:15:53PM -0600, Chris Murphy wrote: Ancient bug, still seems to be a bug.

Re: Problem with file system

2017-11-04 Thread Chris Murphy
On Sat, Nov 4, 2017 at 1:26 AM, Dave wrote: > On Mon, Oct 30, 2017 at 5:37 PM, Chris Murphy wrote: >> >> That is not a general purpose file system. It's a file system for admins who >> understand where the bodies are buried. > > I'm not sure I

Re: Problem with file system

2017-11-04 Thread Chris Murphy
On Fri, Nov 3, 2017 at 10:46 PM, Adam Borowski wrote: > On Fri, Nov 03, 2017 at 04:03:44PM -0600, Chris Murphy wrote: >> On Tue, Oct 31, 2017 at 5:28 AM, Austin S. Hemmelgarn >> wrote: >> >> > If you're running on an SSD (or thinly provisioned storage,

Re: [PATCH 0/8] mkfs: Quota support

2017-11-04 Thread Lu Fengqi
On Fri, Oct 27, 2017 at 03:29:28PM +0800, Qu Wenruo wrote: >This patchset adds quota support, which means the result fs will have >quota enabled by default, and its accounting is already consistent, no >manually rescan or quota enable is needed. > >The overall design of such support is: >1) Create

Re: [PATCH 3/8] btrfs-progs: qgroup-verify: Move qgroup classification out of report_qgroups

2017-11-04 Thread Lu Fengqi
On Fri, Oct 27, 2017 at 03:29:31PM +0800, Qu Wenruo wrote: >The original qgroup-verify integrates qgroup classification into >report_qgroups(). >This behavior makes silent qgroup repair (or offline rescan) impossible. > >To repair qgroup, we must call report_qgroups() to trigger bad qgroup

Re: xfstests:btrfs/025, 026 fails

2017-11-04 Thread Lakshmipathi.G
Okay I narrowed it down to /bin/mount -t btrfs -o context=system_u:object_r:root_t:s0 -o compress /dev/xvdc /mnt/scratch command from xfstests/btrfs/026. Cheers. On 11/4/17, Lakshmipathi.G wrote: > Hi . > > While running xfstests with 4.14.0-rc7 the test hangs on

Re: Problem with file system

2017-11-04 Thread Marat Khalili
>How is this an issue? Discard is issued only once we're positive >there's no >reference to the freed blocks anywhere. At that point, they're also >open >for reuse, thus they can be arbitrarily scribbled upon. Point was, how about keeping this reference for some time period? >Unless your

btrfs-progs crash with segfault on broken filesystem

2017-11-04 Thread Lars Altenhain
Hi, I have a broken btrfs filesystem, which would not mount (even with -o ro,recovery) and I also can't copy any of the data using "btrfs rescue" because the btrfs tool crashes with a segfault. The system is running openSUSE Leap 42.3 with kernel 4.13.3 and I used the latest btrfs-progs compiled

xfstests:btrfs/025, 026 fails

2017-11-04 Thread Lakshmipathi.G
Hi . While running xfstests with 4.14.0-rc7 the test hangs on btrfs/026 (after running 025) and produces below trace: [ 2134.147940] run fstests btrfs/026 at 2017-11-04 09:46:19 [ 2134.388024] BTRFS: device fsid d3de0b02-8b7e-422a-8165-c074f834e909 devid 1 transid 5 /dev/xvdc [ 2134.405001]

Re: Problem with file system

2017-11-04 Thread Dave
On Mon, Oct 30, 2017 at 5:37 PM, Chris Murphy wrote: > > That is not a general purpose file system. It's a file system for admins who > understand where the bodies are buried. I'm not sure I understand your comment... Are you saying BTRFS is not a general purpose file

Re: updatedb does not index /home when /home is Btrfs

2017-11-04 Thread Adam Borowski
On Sat, Nov 04, 2017 at 09:26:36AM +0300, Andrei Borzenkov wrote: > 04.11.2017 07:49, Adam Borowski пишет: > > On Fri, Nov 03, 2017 at 06:15:53PM -0600, Chris Murphy wrote: > >> Ancient bug, still seems to be a bug. > >> https://bugzilla.redhat.com/show_bug.cgi?id=906591 > >> > >> The issue is

Re: updatedb does not index /home when /home is Btrfs

2017-11-04 Thread Andrei Borzenkov
04.11.2017 07:49, Adam Borowski пишет: > On Fri, Nov 03, 2017 at 06:15:53PM -0600, Chris Murphy wrote: >> Ancient bug, still seems to be a bug. >> https://bugzilla.redhat.com/show_bug.cgi?id=906591 >> >> The issue is that updatedb by default will not index bind mounts, but >> by default on Fedora