All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@dilger.ca>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Theodore Ts'o <tytso@mit.edu>,
	Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: ext4: Funny characters appended to file names
Date: Fri, 4 Dec 2020 13:02:32 -0700	[thread overview]
Message-ID: <45B1E6EA-F7E4-4E32-8C63-CCFA662D0F75@dilger.ca> (raw)
In-Reply-To: <fea4dd48-fd8b-823c-0a4b-20ebcd804597@molgen.mpg.de>

[-- Attachment #1: Type: text/plain, Size: 2080 bytes --]

On Dec 4, 2020, at 7:30 AM, Paul Menzel <pmenzel@molgen.mpg.de> wrote:
> 
> Using Debian Sid/unstable with 5.9.11 (5.9.0-4-686-pae), it looks like the last `sudo grub-update` installed modules with corrupted file names. `/boot` is mounted.
> 
>> $ findmnt /boot
>> TARGET SOURCE   FSTYPE OPTIONS
>> /boot  /dev/md0 ext4   rw,relatime
>> $ ls -l /boot/grub/i386-pc/
>> insgesamt 2085
>> -rw-r--r-- 1 root root   8004 13. Aug 23:00 '915resolution.mod-'$'\205\300''u'$'\023\211''鍓]'$'\206\371\377\211\360\350''f'$'\376\377\377\205\300''ur'$'\203\354\004''V'$'\377''t$'$'\030''j'$'\002''胒'
>> -rw-r--r-- 1 root root  10596 13. Aug 23:00 'acpi.mod-'$'\205\300''u'$'\023\211''鍓]'$'\206\371\377\211\360\350''f'$'\376\377\377\205\300''ur'$'\203\354\004''V'$'\377''t$'$'\030''j'$'\002''胒'
>> […]
>> $ file /boot/grub/i386-pc/zstd.mod-��u^S�鍓\]�����f���ur��^DVt\$^Xj^B胒 /boot/grub/i386-pc/zstd.mod-��u�鍓]������f�����ur��V�t$j胒: ELF 32-bit LSB relocatable, Intel 80386, version 1 (SYSV), not stripped
> 
> Checking the file system returned no errors.
> 
>    $ sudo umount /boot
>    $ sudo fsck.ext4 /dev/md0
>    e2fsck 1.45.6 (20-Mar-2020)
>    boot: sauber, 331/124928 Dateien, 145680/497856 Blöcke
> 
> This causes GRUB fail to load the module, and it falls back into rescue mode.
> 
> Any idea, what might have happened. It’s a degraded RAID, and I only use one drive since several years, but never deactivated it, and `/dev/md0` still shows up.
> 
> ```
> $ more /proc/mdstat
> Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
> md0 : active raid1 sdb1[0]
>      497856 blocks [2/1] [U_]
> 
> md1 : active raid1 sdb2[0]
>      1953013952 blocks [2/1] [U_]
> 
> unused devices: <none>
> ```

Did you try downgrading to the previous kernel to see if that fixes the problem?
Then, it would be useful to bisect between the old working kernel and the new
broken kernel to see what introduced this bug.

Cheers, Andreas






[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 873 bytes --]

      parent reply	other threads:[~2020-12-04 20:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-04 14:30 ext4: Funny characters appended to file names Paul Menzel
2020-12-04 15:28 ` Theodore Y. Ts'o
2020-12-04 15:39   ` Paul Menzel
2020-12-04 18:05     ` Theodore Y. Ts'o
2020-12-05 19:34       ` Paul Menzel
2020-12-06 14:44         ` Colin Watson
2020-12-06 15:15           ` Theodore Y. Ts'o
2020-12-06 17:37             ` Colin Watson
2020-12-06 17:44               ` Colin Watson
2020-12-06 18:27           ` Colin Watson
2020-12-07  2:00             ` Dimitri John Ledkov
2020-12-04 20:02 ` Andreas Dilger [this message]

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=45B1E6EA-F7E4-4E32-8C63-CCFA662D0F75@dilger.ca \
    --to=adilger@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=pmenzel@molgen.mpg.de \
    --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.