On 6/29/2022 1:54 AM, Tim via users wrote:
Samuel Sieb:
The journal has nothing to do with memory management. It's about
filesystem protection. btrfs would also be better because it is
always "journaled" (not exactly, but fairly equivalent).
Bill Cunningham:
I thought it was involved in "swapping". Like a swap file my bad.
File system journalling is about all writing to a drive being done as a
sequence (this write, then that update, then the next update). During
a crash, hopefully you only lost the last bit of writing, and what was done before that is still there.
Oh I see. lol Well I added a journal file. In the root ".journal". Then
dumpe2fs says clean now. I have about 30 GB of space with this
filesystem, and I really truthfully don't get errors much; unless they
are small ones. This time there was quite a few. I mounted ro and
changed the fstab file from ext2 to ext3. Seems to be working. I never
really looked into the ext3 or ext4 because ext2 has always worked.
Huge_file support I don't need with a 30 GB space size. I used the
tune2fs -j option too, so there may be some ext3 attribs that aren't
around like dir_ option. But it seems to work. Then I remounted in rw
and saved the fstab and all seems right. Thanks.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
