From: "Libor Klepáč" <libor.klepac@bcom.cz>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Btrfs lockups on ubuntu with bees
Date: Thu, 23 Dec 2021 09:54:16 +0000 [thread overview]
Message-ID: <757a8f5a62644be35a2e06102bbb12fa68f0352e.camel@bcom.cz> (raw)
In-Reply-To: <f6b25f1a-f90c-98c4-6d07-bd76b38572c6@suse.com>
Hi,
On St, 2021-12-15 at 11:48 +0200, Nikolay Borisov wrote:
>
>
> On 15.12.21 г. 11:42, Libor Klepáč wrote:
> >
> > On Po, 2021-12-13 at 17:51 -0500, Zygo Blaxell wrote:
> > > On Thu, Dec 09, 2021 at 09:23:53AM +0000, Libor Klepáč wrote:
> > > > Hi,
> > > > thanks for looking into it.
> > > > More bellow
> > > > ......
> > > > Lockup happened also at second customer, where we tried to use
> > > > this
> > > > solution.
> > > > Good news is, that when we stop bees, it does not happen again
> > > > and
> > > > btrfs scrub says, that all data are ok.
> > > > Bad news is, we will run out of disk space soon ;)
> > >
> > > Downgrading to 5.10.82 seems to work around the issue (probably
> > > also
> > > .83 and .84 too, but we have more testing hours on .82).
> > >
> > Ok, thanks for info. I will try, if we can run this machine with
> > debian
> > kernel from stable - 5.10.x
> >
> > > > Are you interested in trace from kernel? I saved it, but i
> > > > don't
> > > > know,
> > > > if it's the same as before.
> > >
> > > Sure.
> >
> > Here it is
> > https://download.bcom.cz/btrfs/trace5.txt
>
> That's the same issue that Zygo has reported, care to also perform
> the
> steps I outlined in the following email:
>
> https://lore.kernel.org/linux-btrfs/c6125582-a1dc-1114-8211-
> 48437dbf4976@suse.com/T/#m79e9da87b8ec15c40999999d3ffc348f271fbf33
>
>
Sorry, cannot experiment much on those machines.
I went back to kernel 5.10.x , as Zygo suggested.
Also had minor heart attack, when it said "cannot open ctree" on first
boot with that kernel, but it was fine on next mount
Libor
> > >
> > > > Thanks,
> > > > Libor
> > > >
> > > >
> > > > > >
next prev parent reply other threads:[~2021-12-23 9:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 14:36 Btrfs lockups on ubuntu with bees Libor Klepáč
2021-12-09 4:44 ` Zygo Blaxell
2021-12-09 9:23 ` Libor Klepáč
2021-12-13 22:51 ` Zygo Blaxell
2021-12-15 9:42 ` Libor Klepáč
2021-12-15 9:48 ` Nikolay Borisov
2021-12-23 9:54 ` Libor Klepáč [this message]
2021-12-24 11:40 ` Libor Klepáč
2021-12-24 11:49 ` Libor Klepáč
2021-12-31 19:17 ` Zygo Blaxell
2021-12-31 19:24 ` Zygo Blaxell
2022-01-03 10:47 ` Libor Klepáč
2022-01-04 3:09 ` Zygo Blaxell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=757a8f5a62644be35a2e06102bbb12fa68f0352e.camel@bcom.cz \
--to=libor.klepac@bcom.cz \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox