All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pal, Laszlo" <vlad@vlad.hu>
To: Leonidas Spyropoulos <artafinde@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: performance recommendations
Date: Tue, 16 Feb 2021 19:01:47 +0100	[thread overview]
Message-ID: <CAFTxqD_RgvZTPCZywE28nW==PjT5N68_8q7zr1Te-VAiHMp1oQ@mail.gmail.com> (raw)
In-Reply-To: <20210216174906.iv5ylu3p7jn347kb@tiamat>

Hi,

Thank you. If I have to clone, I think I'll just get rid of the
machine and recreate with some other file system. I'm aware, this is
my fault -lack of research and time pressure-, but I think if I can
boot it with the old kernel I'll keep it running as long as it can and
I'll use this time to create another, better designed machine.

Answering your question regarding the ctree, no there is nothing else
in the log but when I check dmesg on the booted rescueCD during mount,
I can see some similar message "btrfs transaction blocked more than
xxx seconds" and the the end "open_ctree", so it seems I really have
some file system corruption as the root cause (maybe created by some
bugs in the old code, or some unexpected reboot)

Thx
Laszlo

On Tue, Feb 16, 2021 at 6:52 PM Leonidas Spyropoulos
<artafinde@gmail.com> wrote:
>
> Hi Laszlo,
>
> On 16/02/21, Pal, Laszlo wrote:
> > Hi,
> >
> > Thank you. So, I've installed a new centos7 with the same
> > configuration, old kernel and using btrfs. Then, upgraded the kernel
> > to 5.11 and all went well, so I thought let's do it on the prod server
> >
> Since this is a VM can you clone the disk / partition and attach it to
> another VM which running a newer kernel and btrfs progs?
>
> This way you can try debugging it without affecting prod server.
>
> > Unfortunately when I boot on 5.11 sysroot mount times out and I have
> > something like this in log
> >
> > btrfs open ctree failed
> So before that `dmesg` doesn't have any relevant logs?
> >
> > Any quick fix for this? I'm able to mount btrfs volume using a rescuCD
> > but I have the same issues, like rm a big file takes 10 minutes....
>
> If you manage to mount the disk in a newer kernel and btrfs progs try
> creating a new file system to take advantage of the new feature (on
> creation) - then migrate the data and follow the recommendations
> mentioned already.
>
> Cheers,
>
> --
> Leonidas Spyropoulos
>
> A: Because it messes up the order in which people normally read text.
> Q: Why is it such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing on usenet and in e-mail?
>

  reply	other threads:[~2021-02-16 18:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-15 14:53 performance recommendations Pal, Laszlo
2021-02-15 19:30 ` Pal, Laszlo
     [not found]   ` <B7BDEFC2-2444-4926-8FFC-D78B6CE5CB4E@vlad.hu>
2021-02-15 21:50     ` Pal, Laszlo
2021-02-16  6:08       ` Piotr Szymaniak
2021-02-16  7:17 ` Nikolay Borisov
2021-02-16  8:54   ` Pal, Laszlo
2021-02-16  9:02     ` Nikolay Borisov
2021-02-16 10:28     ` Lionel Bouton
     [not found]     ` <aeed56c3-e641-46a1-5692-04c6ae75d212@gmail.com>
2021-02-16 17:03       ` Pal, Laszlo
2021-02-16 17:49         ` Leonidas Spyropoulos
2021-02-16 18:01           ` Pal, Laszlo [this message]
2021-02-16 18:21             ` Lionel Bouton
2021-02-16 19:31               ` Pal, Laszlo

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='CAFTxqD_RgvZTPCZywE28nW==PjT5N68_8q7zr1Te-VAiHMp1oQ@mail.gmail.com' \
    --to=vlad@vlad.hu \
    --cc=artafinde@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.