Opened 4 years ago
Closed 14 months ago
#16392 closed bug (fixed)
Multiple issues with ext4 filesystem support
| Reported by: | Parnikkapore | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | File Systems/ext2 | Version: | R1/beta2 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
There are multiple issues with Haiku's ext4 filesystem implementation. Here's what I've found so far...
- Haiku can't mount my Linux install's root filesystem, complaining "bad data". This one will be hard to reproduce.
- A partition mounted read-only in Haiku cannot be mounted in Linux. fsck complains that the superblock is corrupt, but restores it just fine.
- A partition mounted read-write in Haiku got several fsck complaints - there's something about inodes too?
Change History (2)
comment:1 by , 4 years ago
comment:2 by , 14 months ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
There were fixes for a metadata checksum issue in https://cgit.haiku-os.org/haiku/commit/src/add-ons/kernel/file_systems/ext2?id=842a1538a6b726ba535497d7bea7756dc191f90c which would result in bad data by reading and incorrect checksums by writing.
The issue "A partition mounted read-only in Haiku cannot be mounted in Linux." doesn't look like something: this is the common test scenario, which would get multiple bug reports.
Note:
See TracTickets
for help on using tickets.
Experienced precisely the same problem too. Only, my root Linux filesystem is ext4. Upon next Linux boot, fsck complained on some Journal error and performed a file system check, just as described above.