First of all thank you very much for your quickly response.
I am glad to say you we fixed that issue thanks to your post :)
The problem was we formatted the disk (sb5) using some tool from newer Ubuntu
version which put metadata_csum feature on it. And because using on Ubuntu
14.04 it had some
The errors simply mean that ext4 has detected that its metadata has
gotten corrupted. How and why it happened is going to vary from
situation to situation.
For example, in the case of the original reporter, it was due to him
installing ext2fsd, and trying to access the file system from windows.
We have an error quiet similar to this one reported.
We are using Ubuntu 14.04 .. but I really think it's not a matter of version
though.
We are getting randomly the following errors:
--
[97030.025645] EXT4-fs error (device sdb5): ext4_iget:4156: inode #26351669:
comm apache2: checksum
Sorry I attached a wrong file, this one is the correct one!
** Attachment added: "e2fsck_output_ok"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1637779/+attachment/4920266/+files/error_32_1.JPG
--
You received this bug notification because you are a member of Ubuntu
Touch
Also got this issue after using ext2fsd (dual-boot), never had any
issues before
I have attached my dumpe2fs output
** Attachment added: "dumpe2fs.txt"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1637779/+attachment/4790759/+files/dumpe2fs.txt
--
You received this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: e2fsprogs (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
I'm experiencing this exact issue. 16.10 x64, not dual booted. Only
difference is mine is fill disk encrypted, so my device is dm-0.
Let me know what to attach
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in
dumpef2s output attached
when i booted into windows and then back to linux there was always
additional checksum error in superblock. when i was booting only to
linux then there were always errors i wrote in previous comments, but I
don't remember exact numbers
all this started because of damaged
Is it always the same inode number which is reported as having an
invalid checksum?
Can you attach the output of dumpe2fs -h /dev/hdXX (where hdXX should be
replaced with the block device name of your file system)?
--
You received this bug notification because you are a member of Ubuntu
Touch
problem seems to be related to ext2fsd on windows 10 (I have dual boot)
disk corruptions start as soon as I install it and mount the partition. after
it corruptions appear even when I don't boot into windows - probably it damaged
something too bad
--
You received this bug notification because
after failure fsck shows this:
fsck from util-linux 2.28.2
e2fsck 1.43.3 (04-Sep-2016)
/dev/sdb5: recovering journal
Superblock last mount time is in the future.
(by less than a day, probably due to the hardware clock being
incorrectly set)
Pass 1: Checking inodes, blocks, and sizes
11 matches
Mail list logo
