Outputs ext2 in --notarball mode
Bug #437619 reported by
Loïc Minier
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| RootStock |
Fix Released
|
Low
|
Oliver Grawert | ||
Bug Description
Hi
When using --notarball mode, the resulting FS is ext2 which is very fragile. Consider switching to ext3 or ext4 as the temporary filesystem to get a journalised fs as output image in no-tarball mode.
Thanks
Related branches
Revision history for this message
| Oliver Grawert (ogra) wrote | #1 |
Revision history for this message
| Loïc Minier (lool) wrote | #2 |
| Changed in project-rootstock: | |
| status: | New → Fix Committed |
| assignee: | nobody → Oliver Grawert (ogra) |
| importance: | Undecided → Low |
| Changed in project-rootstock: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
ext3 was chosen as the smallest common denominator, defaulting to ext3 definately requires that the kernel for teh target system has a journalling filesystem which may or may not be the case, likelyness that the user compiled a kernel with ext2 support is way higher than expecting a journalling FS imho