Products > Computers
Linux:: EXT4-fs odds?!?
greenpossum:
I think your original mistake was attempting the migration on an unclean ext3 filesystem. The full instructions require that you fix any inconsistencies with fsck.ext3 before running tune2fs. Perhaps that version of tune2fs didn't check for a consistent filesystem, recent versions may. As such you probably got a filesystem that was neither here nor there.
I have done ext3 to ext4 migration many times without issues.
0db:
--- Quote from: greenpossum on April 04, 2020, 08:42:29 am ---I think your original mistake was attempting the migration on an unclean ext3 filesystem. The full instructions require that you fix any inconsistencies with fsck.ext3 before running tune2fs.
--- End quote ---
before tune2fs, I checked it with fsck and it reported no problems.
greenpossum:
Yet, file -s showed that the journal needed recovering. So if the problem didn't happen then it was caused by something else you did. Anyway too late now.
0db:
I seriously think migrating from Ext3 to Ext4 was not good idea
I have a second computer with Ext4 here, it's a server and it crashed a couple of days ago. When checked it reported
--- Code: ---fsck.ext4 -f /dev/hda6
e2fsck 1.44.5 (15-Dec-2018)
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix<y>? yes
Inode 53202 was part of the orphaned inode list. FIXED.
Inode 53203 was part of the orphaned inode list. FIXED.
Inode 53204 was part of the orphaned inode list. FIXED.
Inode 53206 was part of the orphaned inode list. FIXED.
Inode 53207 was part of the orphaned inode list. FIXED.
Inode 70082 was part of the orphaned inode list. FIXED.
Inode 70087 was part of the orphaned inode list. FIXED.
Inode 70095 was part of the orphaned inode list. FIXED.
Inode 70097 was part of the orphaned inode list. FIXED.
Inode 70104 was part of the orphaned inode list. FIXED.
Inode 70106 was part of the orphaned inode list. FIXED.
Inode 74981 was part of the orphaned inode list. FIXED.
Inode 160446 was part of the orphaned inode list. FIXED.
--- End code ---
e2fsck is v1.44.5 (15-Dec-2018) and it was able to check and identifies problems with Ext4 on the crashed server, but not able to report any problem on the computer migrated from Ext3 to Ext4.
... perhaps, because the server is being Ext4 since the beginning ...
0db:
--- Quote from: greenpossum on April 04, 2020, 09:53:18 am ---Yet, file -s showed that the journal needed recovering. So if the problem didn't happen then it was caused by something else you did. Anyway too late now.
--- End quote ---
indeed too late
- badblock to check the integrity of the physical hard drive
- I will repartition it and reformat sdc3 into Xfs
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version