Online check of ext4:
If your filesystem is located on a logical volume (LVM) then I assume you
can make a snapshot and do a check of that.
Make SS:
lvcreate --snapshot --size 1G --name lv_root_SS --chunksize 4k
/dev/VG1/lv_root
EXT4 check:
e2fsck -f /dev/dm-3
Remove SS:
lvremove --yes VG1/lv_r
Will a file system check detect the corruptions?
Can it be done online?
Thank you.
As there were some questions along in this thread let me summarize
some points:
The issue affects fs/ext4 code, so no other filesystems are affected
(e.g. btrfs).
The issue affects all kernels which have the commit 91562895f803
("ext4: properly sync file size update after O_SYNC direct IO") from
On Mon, 11 Dec 2023 10:38:40 +0100 helios.sola...@gmx.ch wrote:
> I have been running debian 12.3 with kernel 6.1.64-1 for a few hours,
> how can I find out whether the file system has been corrupted?
yes, I would also appreciate an explanation who could be affected,
how to diagnose the problem, a
I have been running debian 12.3 with kernel 6.1.64-1 for a few hours,
how can I find out whether the file system has been corrupted?
Hi,
On Sat, Dec 09, 2023 at 03:07:37PM +0100, Salvatore Bonaccorso wrote:
> Source: linux
> Version: 6.1.64-1
> Severity: grave
> Tags: upstream
> Justification: causes non-serious data loss
> X-Debbugs-Cc: debian-rele...@lists.debian.org, car...@debian.org,
> a...@debian.org
>
> Hi
>
> I'm fil
Running the single test with ext4:
# LTP_SINGLE_FS_TYPE=ext4 LTP_DEV_FS_TYPE=ext4 ./preadv03_64
tst_device.c:96: TINFO: Found free device 0 '/dev/loop0'
tst_test.c:1690: TINFO: LTP version: 20230929-194-g5c096b2cf
tst_test.c:1574: TINFO: Timeout per run is 0h 00m 30s
tst_supported_fs_types.c:149:
Source: linux
Version: 6.1.64-1
Severity: grave
Tags: upstream
Justification: causes non-serious data loss
X-Debbugs-Cc: debian-rele...@lists.debian.org, car...@debian.org,
a...@debian.org
Hi
I'm filling this for visibility.
There might be a ext4 data corruption issue with the kernel released
i
8 matches
Mail list logo
