[PATCH v2 1/2] btrfs: make code easy to read in btrfs_open_one_device()

From: Anand Jain First set the usual case that is writeable, then check for any special case like a seed device or a rdonly device and set the state appropriately. Signed-off-by: Anand Jain --- v1->v2: Add comments, and update change log.

[PATCH v2.1 2/2] btrfs: optimize move uuid_mutex closer to the critical section

Move uuid_mutex closer to the exclusion section. Signed-off-by: Anand Jain Reviewed-by: David Sterba --- v2->v2.1: updated the v2 reroll log below. v1->v2: Add received reviewed-by. Thxs. Fix conflict on top of kdave misc-next. fs/btrfs/volumes.c |

Re: Damaged Root Tree(s)

On 2018年01月22日 14:11, Liwei wrote: > Hi Wenruo, > >> On 2018年01月22日 09:11, Qu Wenruo wrote: >>> >>> >>> On 2018年01月22日 03:16, Liwei wrote: Hi list, TLDR > 1. Can I mount a filesystem using one of the roots found with btrfs-find-root? >>> >>> Depends on the tree.

Re: Damaged Root Tree(s)

Hi Wenruo, > On 2018年01月22日 09:11, Qu Wenruo wrote: > > > > > > On 2018年01月22日 03:16, Liwei wrote: > >> Hi list, > >> > >> TLDR > > >> 1. Can I mount a filesystem using one of the roots found with > >> btrfs-find-root? > > > > Depends on the tree. > > > > If it's root tree, it's possible.

[PATCH v2 1/2] btrfs: make code easy to read in btrfs_open_one_device()

From: Anand Jain First set the usual case that is writeable, then check for any special case like a seed device or a rdonly device and set the state appropriately. Signed-off-by: Anand Jain --- v1->v2: Add comment and commit log to explain its

[PATCH v2] btrfs: Add chunk allocation ENOSPC debug message for enospc_debug mount option

Enospc_debug makes extent allocator to print more debug messages, however for chunk allocation, there is no debug message for enospc_debug at all. This patch will add message for the following parts of chunk allocator: 1) No rw device at all Quite rare, but at least output one message for

[PATCH v2 2/2] btrfs: optimize move uuid_mutex closer to the critical section

Move uuid_mutex closer to the exclusion section. Signed-off-by: Anand Jain Reviewed-by: David Sterba --- v1->v1: No change. Add received reviewed-by. Thxs. fs/btrfs/volumes.c | 17 - 1 file changed, 8 insertions(+), 9 deletions(-)

[PATCH v2.1 2/3] btrfs-progs: dir-item: Don't do extra filetype validaction check for btrfs_match_dir_item_name

verify_dir_item() is called in btrfs_match_dir_item_name() to ensure we won't search beyond item boundary and does extra filetype check. However in the follow call chain, such extra filetype check can cause problems: 1) btrfs_add_link() |- check_dir_conflict() |-

Re: [PATCH 1/3] btrfs: make code easy to read in btrfs_open_one_device()

On 01/05/2018 10:09 PM, David Sterba wrote: On Fri, Dec 15, 2017 at 03:40:14PM +0800, Anand Jain wrote: No functional change. First set the usual case, writeable then check for any special config. Signed-off-by: Anand Jain --- fs/btrfs/volumes.c | 8 +++- 1

Re: [PATCH] btrfs: remove spurious WARN_ON(ref->count) in find_parent_nodes

On Sun, Jan 21, 2018 at 02:08:58PM -0500, Zygo Blaxell wrote: >This warning appears during execution of the LOGICAL_INO ioctl and >appears to be spurious: > > [ cut here ] > WARNING: CPU: 3 PID: 18172 at fs/btrfs/backref.c:1391 > find_parent_nodes+0xc41/0x14e0

Re: Damaged Root Tree(s)

Hi Chris, > On Sun, Jan 21, 2018 at 12:16 PM, Liwei wrote: > > Hi list, > > > > TLDR > > 1. Can I mount a filesystem using one of the roots found with > > btrfs-find-root? > > Not necessarily because more than just the tree root needs to be > readable to do a mount.

Re: Damaged Root Tree(s)

On 2018年01月22日 09:11, Qu Wenruo wrote: > > > On 2018年01月22日 03:16, Liwei wrote: >> Hi list, >> >> TLDR >> 1. Can I mount a filesystem using one of the roots found with >> btrfs-find-root? > > Depends on the tree. > > If it's root tree, it's possible. > > Otherwise those found trees

Re: Damaged Root Tree(s)

On 2018年01月22日 03:16, Liwei wrote: > Hi list, > > TLDR > 1. Can I mount a filesystem using one of the roots found with btrfs-find-root? Depends on the tree. If it's root tree, it's possible. Otherwise those found trees don't help much. > 2. Can btrfs check just fix the damaged root

Re: btrfs volume corrupt. btrfs-progs bug or need to rebuild volume?

On 2018年01月22日 04:33, Rosen Penev wrote: > On Sun, Jan 21, 2018 at 1:53 AM, Qu Wenruo wrote: >> >> >> On 2018年01月20日 05:45, Rosen Penev wrote: >>> v2: Add proper subject >>> >>> I've been playing around with a specific kernel on a specific device >>> trying to figure out

Re: Periodic frame losses when recording to btrfs volume with OBS

On 2018年01月21日 23:27, Sebastian Ochmann wrote: > On 21.01.2018 11:04, Qu Wenruo wrote: >> >> >> On 2018年01月20日 18:47, Sebastian Ochmann wrote: >>> Hello, >>> >>> I would like to describe a real-world use case where btrfs does not >>> perform well for me. I'm recording 60 fps, larger-than-1080p

Re: Can't mount (even in ro) after power outage - corrupt leaf, open_ctree failed

On Sun, Jan 21, 2018 at 4:13 PM, Chris Murphy wrote: > On Sun, Jan 21, 2018 at 3:31 PM, msk conf wrote: >> Hello, >> >> thank you for the reply. >> >>> What do you get for btrfs fi df /array >> >> >> Can't do that because filesystem is not mountable.

Re: Periodic frame losses when recording to btrfs volume with OBS

On 21.01.2018 23:04, Chris Murphy wrote: On Sun, Jan 21, 2018 at 8:27 AM, Sebastian Ochmann wrote: On 21.01.2018 11:04, Qu Wenruo wrote: The output of "mount" after setting 10 seconds commit interval: /dev/sdc1 on /mnt/rec type btrfs

Re: Periodic frame losses when recording to btrfs volume with OBS

On Sun, Jan 21, 2018 at 8:27 AM, Sebastian Ochmann wrote: > On 21.01.2018 11:04, Qu Wenruo wrote: > The output of "mount" after setting 10 seconds commit interval: > > /dev/sdc1 on /mnt/rec type btrfs > (rw,relatime,space_cache,commit=10,subvolid=5,subvol=/) I wonder if

Re: Can't mount (even in ro) after power outage - corrupt leaf, open_ctree failed

On Sun, Jan 21, 2018 at 8:53 AM, msk conf wrote: > Hello there, > > I would like to ask you for help with (corrupted) btrfs on my nas. > > After power outage I can't mount it back at all: > UUID="e8cb7e76-7f93-4eac-aec7-ca64395d2110"/array btrfs > noatime,compress=lzo

Re: Damaged Root Tree(s)

On Sun, Jan 21, 2018 at 12:16 PM, Liwei wrote: > Hi list, > > TLDR > 1. Can I mount a filesystem using one of the roots found with btrfs-find-root? Not necessarily because more than just the tree root needs to be readable to do a mount. But decent chance it's

Re: btrfs volume corrupt. btrfs-progs bug or need to rebuild volume?

On Sun, Jan 21, 2018 at 1:53 AM, Qu Wenruo wrote: > > > On 2018年01月20日 05:45, Rosen Penev wrote: >> v2: Add proper subject >> >> I've been playing around with a specific kernel on a specific device >> trying to figure out why btrfs keeps throwing csum errors after ~15 >>

Darlehen

Benötigen Sie Privat- oder Geschäftskredite ohne Stress und schnelle Zustimmung? Wenn ja, kontaktieren Sie uns bitte alexgr...@gmail.com -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at

Damaged Root Tree(s)

Hi list, TLDR 1. Can I mount a filesystem using one of the roots found with btrfs-find-root? 2. Can btrfs check just fix the damaged root without attempting any other repairs? 3. If the above is not possible, how should I proceed given that I seem to have lost both the main and backup

[PATCH] btrfs: remove spurious WARN_ON(ref->count) in find_parent_nodes

This warning appears during execution of the LOGICAL_INO ioctl and appears to be spurious: [ cut here ] WARNING: CPU: 3 PID: 18172 at fs/btrfs/backref.c:1391 find_parent_nodes+0xc41/0x14e0 Modules linked in: ib_iser rdma_cm iw_cm ib_cm ib_core

Can't mount (even in ro) after power outage - corrupt leaf, open_ctree failed

Hello there, I would like to ask you for help with (corrupted) btrfs on my nas. After power outage I can't mount it back at all: UUID="e8cb7e76-7f93-4eac-aec7-ca64395d2110"    /array  btrfs noatime,compress=lzo    0   2 UUID="e8cb7e76-7f93-4eac-aec7-ca64395d2110"    /home   btrfs

Re: Periodic frame losses when recording to btrfs volume with OBS

On 21.01.2018 11:04, Qu Wenruo wrote: On 2018年01月20日 18:47, Sebastian Ochmann wrote: Hello, I would like to describe a real-world use case where btrfs does not perform well for me. I'm recording 60 fps, larger-than-1080p video using OBS Studio [1] where it is important that the video stream

Re: Periodic frame losses when recording to btrfs volume with OBS

On 2018年01月20日 18:47, Sebastian Ochmann wrote: > Hello, > > I would like to describe a real-world use case where btrfs does not > perform well for me. I'm recording 60 fps, larger-than-1080p video using > OBS Studio [1] where it is important that the video stream is encoded > and written out to

Re: btrfs volume corrupt. btrfs-progs bug or need to rebuild volume?

On 2018年01月20日 05:45, Rosen Penev wrote: > v2: Add proper subject > > I've been playing around with a specific kernel on a specific device > trying to figure out why btrfs keeps throwing csum errors after ~15 > hours. I've almost nailed it down to some specific CONFIG option in > the kernel,