need short paragraph of techno babble translated (about use of /dev/loop)
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
need short paragraph of techno babble translated (about use of /dev/loop)
Quote:
2.2. Use of journaling file systems on loop device
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Don't use a journaling file system on top of file backed loop device. Device
backed loop device can be used with journaling file systems as device backed
loops guarantee that writes reach disk platters in order required by
journaling file system (write caching must be disabled on the disk drive, of
course). With file backed loop devices, correct write ordering may extend
only to page cache (which resides in RAM) of underlying file system. VM can
write such pages to disk in any order it wishes, and thus break write order
expectation of journaling file system.
im going to use loop-aes from loop-aes.sourceforge.net to make an encrypted filesystem image.
am i right, in thinking that the about, is telling me that after i have setup the encrypted loop (pointing to /home/user/filesystemimage)
i should format it as a NON journalling file system (like ext2)
im sure last time i did this i used ext3 !
or maybe its saying dont make a jourrnaling file ssytem withing the encrypted file system ?
AGH !!!!!
help !
OK.. my root filesystem is reiserfs.
and on this root filesystem i have a file BIGFILE.fs
i pointed loop1 at it with losetup.
and i formated it with mkfs.ext2 /dev/loop1
im not using a journalling filesystem with the loop.. but the whole lot is built on top of the root file system. from what i understand, this setup IS okay ?
Yes, you should be ok with that setup. As far as I can tell, the documentation above applies only to the filesystem you are creating on the loopback file (ext2 in this case); not the actual filesystem the loopback file lives in (reiserfs).
just to be sure, i made a 100meg file from /dev/urandom in the encrypted file system, and noted its md5sum.
after many read / writes mounts and re-boots, the md5 has remained constant, which has to be a good sign.
lol... I nearly had a heart attack. I thought you meant you had an md5sum of the file you were using as a loopback, and after writing to the loopback file, the md5 hash stayed the same. That would definitely not be a good thing.
It took a second for it to sink in that the md5sum was for the random file within the loopback file and that you were writing to other files in the loopback.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.