Re: Is request_firmware() really safe to call in resume callback when /usr/lib/firmware is on btrfs?

2021-04-03 Thread Lukas Middendorf
On 02/04/2021 20:02, Luis Chamberlain wrote: No sorry, I dropped the ball on this but I managed to now spawn up the virtual guests where I was doing development to reproduce this. Give me some time and I will zero in on this now. For now what I have is the following to test this, I next will w

Re: [PATCH v3 00/13] btrfs: support read-write for subpage metadata

2021-04-03 Thread David Sterba
On Thu, Mar 25, 2021 at 03:14:32PM +0800, Qu Wenruo wrote: > This patchset can be fetched from the following github repo, along with > the full subpage RW support: > https://github.com/adam900710/linux/tree/subpage > > This patchset is for metadata read write support. > Qu Wenruo (13): > btrfs:

Re: Is request_firmware() really safe to call in resume callback when /usr/lib/firmware is on btrfs?

2021-04-03 Thread Lukas Middendorf
Hi Luis, I now succeeded in reproducing this in VirtualBox running a F34 minimal installation with / on btrfs (with default firmware files). I can send you the virtual disk file if you want it. With the kernel sourcecode and the compiled and installed kernel it currently is 21.8GiB. On 03/04

Re[6]: Filesystem sometimes Hangs

2021-04-03 Thread Hendrik Friedel
Hello Chris, thanks for your reply. >Remove the discard mount option for this file system and see if that >fixes the problem. Run it for a week or two, or until you're certain >the problem is still happening (or certain it's gone). Some drives >just can't handle sync discards, they become r

Re: BTRFS error (device sda1): bdev /dev/sdb1 errs: wr 2702175, rd 2719033, flush 0, corrupt 6, gen 0

2021-04-03 Thread Lukas Straub
On Fri, 2 Apr 2021 22:46:25 +0200 Thomas <74cmo...@gmail.com> wrote: > Hi, > > I finished repartition of devices /dev/sda + /dev/sdb now. > On both devices the first partition is equal in size: > $ sudo fdisk -l /dev/sda > Festplatte /dev/sda: 238,47 GiB, 256060514304 Bytes, 500118192 Sektoren >

Re: Is request_firmware() really safe to call in resume callback when /usr/lib/firmware is on btrfs?

2021-04-03 Thread Luis Chamberlain
On Sat, Apr 03, 2021 at 12:24:07PM +0200, Lukas Middendorf wrote: > > On 02/04/2021 20:02, Luis Chamberlain wrote: > > No sorry, I dropped the ball on this but I managed to now spawn up the > > virtual guests where I was doing development to reproduce this. Give > > me some time and I will zero in

Re: Is request_firmware() really safe to call in resume callback when /usr/lib/firmware is on btrfs?

2021-04-03 Thread Luis Chamberlain
On Sat, Apr 03, 2021 at 08:25:38PM +, Luis Chamberlain wrote: > So creating say 1000 random files in /lib/firmware on a freshly created > btrfs partition helps reproduce: > > mkfs.btrfs /dev/whatever > mount /dev/wahtever /lib/firmware > # Put it on /etc/fstab too > > Generate 1000 random fil

Re: Is request_firmware() really safe to call in resume callback when /usr/lib/firmware is on btrfs?

2021-04-03 Thread Lukas Middendorf
Great to hear that you now succeeded in reproducing the problem. On 03/04/2021 22:25, Luis Chamberlain wrote: On Sat, Apr 03, 2021 at 12:24:07PM +0200, Lukas Middendorf wrote: One further thing I noticed which might be problematic in rare cases: According to the kernel debug messages, the fir

kernel BUG at fs/btrfs/tree-mod-log.c:675 - misc-next 9228ad80f849 (Mar 29 2021)

2021-04-03 Thread Zygo Blaxell
Base kernel is 9228ad80f849 "btrfs: zoned: move log tree node allocation out of log_root_tree->log_mutex" from misc-next on 2021-03-29. The BUG() moved, but we are still hitting it: [145427.426011][ T5492] BTRFS info (device dm-0): balance: canceled [145427.689964][ T4811] ---