All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mia <9speysdx24@kr33.de>
To: "Patrik Lundquist" <patrik.lundquist@gmail.com>,
	"Qu Wenruo" <quwenruo.btrfs@gmx.com>
Cc: "Linux Btrfs" <linux-btrfs@vger.kernel.org>
Subject: Re: filesystem corrupt - error -117
Date: Tue, 26 Oct 2021 17:28:14 +0000	[thread overview]
Message-ID: <emb611c0ff-705d-4c01-b50f-320f962f39fb@rx2.rx-server.de> (raw)
In-Reply-To: <CAA7pwKOrgt6syr5C3X1+bC14QXZEJ+8HTMZruBBPBT574zNkkQ@rx2.rx-server.de>

Hi Patrik,

good suggestion, I'm on 5.10.0-0.bpo.8-amd64 #1 SMP Debian 
5.10.46-4~bpo10+1 (2021-08-07) now.

Hi Qu,
regarding the memtest. This is a virtual machine, I have no access to 
the host system.
I don't know if a memtest inside the vm would bring legit results?

Regards
Mia

------ Originalnachricht ------
Von: "Patrik Lundquist" <patrik.lundquist@gmail.com>
An: "Mia" <9speysdx24@kr33.de>
Cc: "Linux Btrfs" <linux-btrfs@vger.kernel.org>
Gesendet: 26.10.2021 16:12:45
Betreff: Re: filesystem corrupt - error -117

>On Tue, 26 Oct 2021 at 09:15, Mia <9speysdx24@kr33.de> wrote:
>>
>>  Problem with updating is that this is currently still Debian 10 and a
>>  production environment and I don't know when it is possible to upgrade
>>  because of dependencies.
>
>Maybe you can install the buster-backports kernel which currently is 5.10.70?
>
>https://backports.debian.org/Instructions/


  parent reply	other threads:[~2021-10-26 17:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <em969af203-04e6-4eff-a115-1129ae853867@frystation>
2021-10-25  8:46 ` filesystem corrupt - error -117 Mia
2021-10-25 10:53   ` Qu Wenruo
2021-10-25 10:55     ` Qu Wenruo
     [not found]     ` <69109d24-efa7-b9d1-e1df-c79b3989e7bf@rx2.rx-server.de>
2021-10-25 11:13       ` Mia
2021-10-25 11:14         ` Qu Wenruo
2021-10-25 11:18           ` Qu Wenruo
     [not found]           ` <884d76d1-5836-9a91-a39b-41c37441e020@rx2.rx-server.de>
2021-10-25 17:09             ` Mia
2021-10-25 22:45               ` Qu Wenruo
     [not found]               ` <3ce1dd17-b574-abe3-d6cc-eb16f00117cc@rx2.rx-server.de>
2021-10-26  6:03                 ` Mia
2021-10-26  7:24                   ` Qu Wenruo
2021-10-26 11:18                     ` Robert Krig
2021-10-26 14:12                   ` Patrik Lundquist
     [not found]                   ` <CAA7pwKOrgt6syr5C3X1+bC14QXZEJ+8HTMZruBBPBT574zNkkQ@rx2.rx-server.de>
2021-10-26 17:28                     ` Mia [this message]
2021-10-27  2:49                       ` Qu Wenruo
     [not found]                     ` <emb611c0ff-705d-4c01-b50f-320f962f39fb@frystation>
2021-12-11  8:20                       ` Mia
     [not found]                       ` <embddc7343-8fdf-4be8-87d8-644e20ea86c0@frystation>
2021-12-11  8:28                         ` Mia
2021-12-11  8:39                           ` Qu Wenruo
     [not found]                           ` <29fcb603-506f-d721-5214-2870ce2f8773@rx2.rx-server.de>
2021-12-11  9:10                             ` Mia
     [not found]                             ` <em7854e1bc-eb3d-43a3-abc7-c6ed3e1a167a@frystation>
2021-12-11  9:12                               ` Mia
2021-12-11  9:19                                 ` Qu Wenruo
     [not found]                                 ` <114dbcbb-c0ad-6ffd-f9ff-7aff031d03b5@rx2.rx-server.de>
2021-12-11  9:34                                   ` Mia

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=emb611c0ff-705d-4c01-b50f-320f962f39fb@rx2.rx-server.de \
    --to=9speysdx24@kr33.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=patrik.lundquist@gmail.com \
    --cc=quwenruo.btrfs@gmx.com \
    /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.