All of lore.kernel.org
 help / color / mirror / Atom feed
From: Salvatore Bonaccorso <carnil@debian.org>
To: dud225 <dud225@hotmail.com>,
	1039883@bugs.debian.org, Theodore Ts'o <tytso@mit.edu>,
	Andreas Dilger <adilger.kernel@dilger.ca>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Bug#1039883: linux-image-6.3.0-1-amd64: ext4 corruption with symlinks
Date: Sat, 1 Jul 2023 17:35:21 +0200	[thread overview]
Message-ID: <ZKBHuRSrs96JDZjY@eldamar.lan> (raw)
In-Reply-To: <168802788716.2369531.1979971093539266086.reportbug@ariane.home>

Control: tags -1 + upstream

Hi,

On Thu, Jun 29, 2023 at 10:38:07AM +0200, dud225 wrote:
> Package: linux-image-6.3.0-1-amd64
> Version: linux-image-6.3.0-1-amd64
> Severity: important
> Tags: upstream
> X-Debbugs-Cc: dud225@hotmail.com
> 
> Hello
> 
> I've stored data on a USB external hard drive using ext4 over LUKS2 and I'm getting the following error:
> 	kernel: EXT4-fs error (device dm-11): ext4_map_blocks:607: inode #8159552: block 959787320: comm git-annex:w: lblock 0 mapped>
> 
> I then stumbled upon that kernel bug [1] which matches my case as git-annex is making heavy use of symlinks. However I've faced this issue on the kernel 6.3.0 (linux-image-6.3.0-1-amd64 version 6.3.7-1) so it doesn't look to be actually addressed.
> 
> I've got 3 disks, 2 HDDs and 1 SSD, and oddly the failure only happens on the HDD, the SSD is running fine.
> After reformatting my HDD without the inline_data feature, the issue has disappeared.
> 
> [1] https://bugzilla.kernel.org/show_bug.cgi?id=216317

I believe this should be reported upstream, doing so now to get some
ideas from Ted and Andreas. 

Ted, Andreas the above was reported in Debian at
https://bugs.debian.org/1039883 .

Any insights here?

Regards,
Salvatore

       reply	other threads:[~2023-07-01 15:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <168802788716.2369531.1979971093539266086.reportbug@ariane.home>
2023-07-01 15:35 ` Salvatore Bonaccorso [this message]
     [not found] ` <ZL5DB7vU3GnIx588@eldamar.lan>
     [not found]   ` <2002858.macj2W6JUv@bagend>
     [not found]     ` <DB4PR02MB936085F4449207358A9943568FABA@DB4PR02MB9360.eurprd02.prod.outlook.com>
2024-06-10 16:03       ` linux: ext4 corruption with symlinks Ben Hutchings
2024-06-14 16:18         ` Luis Henriques
2024-06-18  9:52           ` Luis Henriques
2024-06-18 13:19             ` Luis Henriques

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=ZKBHuRSrs96JDZjY@eldamar.lan \
    --to=carnil@debian.org \
    --cc=1039883@bugs.debian.org \
    --cc=adilger.kernel@dilger.ca \
    --cc=dud225@hotmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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.