Search results for query: ext3

My results on my laptop: slippy# uname -a FreeBSD slippy 15.0-CURRENT FreeBSD 15.0-CURRENT #36 komquats-n273622-9d4428ad0239: Thu Nov 14 07:29:01 PST 2024 root@slippy:/export/obj/opt/src/git-src/amd64.amd64/sys/BREAK amd64 slippy# slippy# time dd if=/dev/zero of=/mnt/test.file bs=1M...

On the same machine (Lenovo ThinkCentre M600 Tiny Thin Client N3000 terminal), installing pure FreeBSD 14.1 (UFS fs) and Debian (EXT3 fs) distributions, the disk performance results are dramatically different. Result from dmesg (FreeBSD): ada0 at ahcich1 bus 0 scbus1 target 0 lun 0 ada0...

...to journal user data as well, then use gjournal. Their paradigms are different. Talking about different paradigms, all other filesystems, i.e. EXT3/4, XFS, NTFS, JFS, BTRFS, and ZFS, only use the journal for metadata writes, just like su+j does with (file deletes). None of them journal user...

I don't know. The ZFS port for Windows is brand new and I never tried it. It certainly integrates with the drive system. It is reported as basically working. You could mount readonly if you are afraid of data corruption.

Could I mount a ZFS partition/drive on Windows easy (like it just showing up as a drive in Computer/explorer)? I haven't messed with other filesystems on Windows in years but I recall needing a 3rd-party driver for ext3/4. I'd probably only use it under Windows 10 (21H2) or 11 (24H2+).

...better in some cases while GJ was better for others. You can't make blanket statements like this. We also need to keep in mind that su+j, ZFS, EXT3/4, XFS, JFS and BTRFS journal metadata only. Gjournal is a block level journal. It journals everything. Metadata and data. Yes, with GJ there is...

Older, and uses fusefs which it is said doesn't need to be used now. Mouting Linux Filesystems (ext2/ext3/ext4)

How mature is FreeBSD for reading file systems? It is perfectly possible to read/write file systems such as ext3 and ext4, using the ext2fs module that FreeBSD provides. However, I saw reports here on the forum that using ext2fs would be risky, due to the risk of data corruption or any other...

I will need to get a linux pc first. Thanks this far

Says it all. You need to put it in Linux and recover or delete the Journal. The only way to use ext3/4 on FreeBSD is to disable Journal. Otherwise FreeBSD corrupts it.

...fsck.ext4: Bad magic number in super-block while trying to open /dev/da1p7 The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the...

...to ever happen! So when my Ubuntu 20.04 mounted automatically I've assumed that everything was ok! > How I created the filesystem when I tried EXT3: The drive wasn't mounted of course, I run: mkfs.ext3 /dev/da0p1 After this, I mounted the partition and issued a `mkdir test` in the mounted...

Please tell us more detail. How did you format the file system on the partition? Hint: I would never trust non-native file systems, other than in read-only mode. If you want to create an ext<n> file system, do so on Linux. What file system type did you actually create, ext2 or ext4? How did...

...between FreeBSD and Linux. Update: I've decided to do exactly the same steps as described before with two minor modifications: Create an EXT3 partition, write a "test" directory to it. Go to Linux plug the drive, copy some files and get the drive back to FreeBSD. Now I'm able only to mount...

This is the answer. All modern linux use Journaled ext3 and ext4. Simply turn it off on Linux end and our stuff works. We don't support ext3 or ext4 journaling. Writes crash the fs journal and needs mending in Linux after attempted writes from FreeBSD..

You've been doing FreeBSD for some years now - you should know how to check. FWIW here are the "ext2fs" man pages root@kg-core2:~ # apropos ext2fs ext2fs, ext4fs(5) - ext2/ext3/ext4 file system fsck_ext2fs(8) - compatibility wrapper for e2fsck

Which man page exactly? fusefs-ext2 fusefs-ext4fuse fusefs-lkl How do I check? Could my problem be related to UUIDs?

From the man page "It currently implements most of the features required by ext3 and ext4 file systems. Support for Extended Attributes in ext4 is experimental. Journalling and encryption are currently not supported.". Check if your ext4 fs uses any of the unsupported features.

...Support seems to be continually changing and it is difficult keeping uptodate. The 'alien' filesystems I expose myself to include ext2, ext3, ext4, msdos, ntfs, exfat. I see that I have an ext2fs.ko module loaded. Do I also need to install fusefs-ext2? I note there is also a fuse-ext2...

To quote the man page from ext4magic: "The deletion of files in ext3/4 filesystems can not be easily reversed. Zero out of the block references in the Inodes makes that impossible. Experience with other programs have proved, it is often possible, to restore sufficient...