...data back from the fridge...
Yes...but...did I learn something from that?
I did do installs, and got a complete desktop going...
So, the type is EXT3, for sure. ZFS and GPT should be attempted, the home may have to stay EXT3...unless an in-place format-and-move of the data can be done...
I'm...
Last I heard ext3 and ext4 are read-only.
They are soft journaling filesystems and FreeBSD has no mechanism to handle Linux filesystem journaling.
Even fusefs only mounts them read only.
I also had trouble with FreeBSD messing up the journal after fusefs mounting, so back on Linux I had to fix...
Thanks for the info.
Not that you asked but, I built a new box recently with Ryzen 7 to run my 2012r2 server (web and exchange and media file server (hence my four 4tb NTFS drives)). To my annoyance there is no driver support for 2012r2 or 8.1
They are trying to push me to 2016 version of the...
kldload ext2fs
Read Only supported right in base. You have to use fusefs to write EXT4. Bah. That seems so trivial to me.
https://www.freebsd.org/doc/handbook/filesystems-linux.html
The EXT3 and EXT4 filesystem journaling is borked but the fs works fine overall.
...the grub2 menu. Grub4dos doesn't support booting OpenBSD bsd.rd whereas grub2 does (I have OpenBSD on my third partition). Second partition is ext3 as that can be mounted as though ext4 under Debian, but mounted as though ext2 by OpenBSD, so that's my 'data' partition where the data can be...
All this may be true. And why do you care?
Look at it this way. What is the state of a file system? It is that total of everything that can be observed about a file system. How do you observe a file system? By reading it. You can read directories (that's done with the readdir() system...
...system with the "ro" option doesn't guarantee that a kernel driver will not write to a corresponding block device"
- "ro options don't protect Ext3/4 file systems against automatic orphan inodes deletion performed by a kernel driver on a "read-only" file system and there is no explicit...
Correct. No one in their right mind would add a Linux filesystem library which got released under any other license but the GPL. For the simple reason that doing so would violate said GPL which would open up an enormous can of worms.
It would appear that you don't realize this small fact, but...
They will never implement it for you despite you've spend your own writing an ext2.ko, ext3.ko, ext4.ko, jfs.ko, xfs.ko, btrfs.ko... with a BSD license. Everything they could throw to you now is: ZFS is superior, why use that Linux sh*t :mad:
...risk of data corruption if the filesystem is journalised)
sysutils/fusefs-ext2 : looking to the description, this port seems to support ext2, ext3, ext4 in read and write mode
sysutills/fusfefs-lkl : via linux kernel as a library. This port supports in read and write mode BTFRS, XFS, EXT3...
From what I have heard Red Hat dropped BTRFS because Red Hat only has XFS developers and none BTRFS developers, so they could not modify/develop BTRFS the way they wanted, also they invested heavily in XFS already ...but XFS is dead end (no data consistency, no compression, no deduplication...
...and they put some serious money in that project...
We have 2 3rd party application servers running with SLES in VMs - both use traditional ext3/4. I've had a chat with the support guy who did the last major upgrade for one of those over lunch, and he also talked a bit about their internal...
...are themselves possibly portable, and not all of those devices may be OK with more powerful/complicated file systems. I'd tend to use EXT2 or EXT3 in this circumstance.
EXT2 might not be a good option if there's very much writing (has no journaling), but may be OK for personal mainly read...
I'm pretty sure that nowadays ZFS can be supported as a kernel module in Linux.
I'm not sure if most Linux distros have that as a package or support it with a modified kernel compilation, but I'm sure that Manjaro Linux supports ZFS as kernel module installing extra packages
...# ls /dev/da*
/dev/da0 /dev/da0s1
root@E6420:~ # mount -t ext2fs /dev/da0s1 /mnt
root@E6420:~ # file -s /dev/da0s1
/dev/da0s1: Linux rev 1.0 ext3 filesystem data, UUID=de3dcbc9-a5c5-472a-9395-5756f84c26d6 (needs journal recovery) (large files)
I am using it in R+W mode and it works.
...(3 Tb is long). So, better to have a portable disk that can be either plug on Linux or BSD.
I wanted to have a good FS, without risk for data. EXT3 is definitely reliable. UFS2 too. Both are default FS, but wont be supported by default by Unix on both at the same time. (I mean of course read...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.