Changes between Initial Version and Version 2 of Ticket #18137


Ignore:
Timestamp:
Dec 14, 2022, 5:46:37 PM (2 years ago)
Author:
bipolar
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #18137 – Description

    initial v2  
    1515I thought... why ramfs is setting B_FS_IS_PERSISTENT?
    1616
    17 (In an attempt to fix the issue with the VM preflet, I've tried removing B_FS_IS_PERSISTENT from ramfs, but that cause KDLs when you attempt to write to a RAMFS you just mounted).
     17(In an attempt to fix the issue with the VM preflet, I've tried removing B_FS_IS_PERSISTENT from ramfs, but that cause KDLs when you attempt to write to a RAMFS you just mounted). [Note 1]
    1818
    1919
    … …  
    2222
    2323In that case... Is there a way to check for "the other meaning" of persistent (as in... "you can reasonably expect data to survives reboots"? (seems something backup software, for example, might care about).
     24
     25---
     26
     27Edit: [Note 1]
     28
     29After a second attempt, I couldn't reproduce the KDLs after removing B_FS_IS_PERSISTENT, but doing:
     30
     31{{{
     32mkdir ~/test_ramfs
     33mount -t ramsfs ~/test_ramfs
     34touch ~/test_ramfs/test.txt
     35}}}
     36
     37Also creating a "New Folder" there from Tracker... Then, when attempting to remove that "test.txt" file and "New Folder" from Tracker... caused both Terminal and Tracker to hand and become unkillable.
     38
     39(system wide ramfs was disabled from the boot menu when testing the modified one, of course).