| 1 |
Hello, |
| 2 |
|
| 3 |
I see this msg in /var/log/dmesg: |
| 4 |
|
| 5 |
[ 4.444826] EXT2-fs (sdb3): error: couldn't mount because of |
| 6 |
unsupported optional features (2c0) |
| 7 |
[ 4.468074] EXT4-fs (sdb3): mounted filesystem with ordered data |
| 8 |
mode. Opts: (null) |
| 9 |
|
| 10 |
but my system boots. Is the (2c0) the clue to what features are meant? |
| 11 |
|
| 12 |
Next question: |
| 13 |
|
| 14 |
From this article: |
| 15 |
|
| 16 |
/https://opensource.com/article/18/4/ext4-filesystem/ |
| 17 |
|
| 18 |
I get a good description of *journal*, *ordered* and *writeback* |
| 19 |
journaling levels and I wonder if my root filesystem should have |
| 20 |
*ordered* mode. I recently had a total crash of my ext3/4 root and |
| 21 |
home filesystems, where the directories were lost and I had to paste |
| 22 |
everything back together again by guess and by golly. In decades of |
| 23 |
linux usage, that's never happened to me on that scale. I'd hoped for |
| 24 |
more from journaling filesystems. |
| 25 |
|
| 26 |
Did it happen only because gentoo gave me *ordered* data mode by |
| 27 |
default and I should have had *journal*? |
Archives