Reading FreeBSD filesystems

Reading FreeBSD filesystems

[Benjamin Walkenhorst]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello everybody,

I have both SuSE Linux 7.3 with kernel linux-2.4.20 (2.4.21 was pretty 
unstable on my machine...) and FreeBSD 5.1 installed on my machine. 
As for linux, / and /usr are on ext3-partitions, which I can read just fine 
from FreeBSD using the ext2 driver.
The FreeBSD disklabel is visible and readable from Linux. But I do encounter 
some pretty weird read-errors - or some other kind of problem, as I don't get 
error messages exactly. 
When I read my FreeBSD partitions, some files and folders seem to be missing, 
while others I did already rm under FreeBSD still seem to be present. As 
FreeBSD has shut down correctly before, I don't think this is caused by some 
softupdates-problem or filesystem-inconsitency. On the other hand, I cannot 
see how Linux should still be able to read files that have already been 
removed. I cannot really see how even the buggiest filesystem driver in the 
world might present me with files already removed (and, yes, the content is 
just what it was before the file was erased).
When I read my FreeBSD partitions from Linux, I see the filesystem as it was 
some time ago... two weeks, maybe. Another weird thing is the CDATE, though 
that doesn't matter really: Linux says, all the files on my FreeBSD 
partitions have January 1st, 1970 for CDATE. =) 
But the real problem is Linux looking into the past when reading my FreeBSD 
partitions... 

So has anyone experience with similar problems and maybe even a solution?

Thanks in advance,

kind regards,

Benjamin

- -- 
"Der Hoffnung beraubt sein,
 heiflt noch nicht - verzweifeln."
(Albert Camus)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Public Key available at http://www.krylon.de

iD8DBQE/DxNNoYumWdMvhMQRAh0hAJ9piCvrXnSdAACTauGPpfy6V4mPBACfSBvx
za7qMI68YnlmGdlVtuV1NzU=
=vJim
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Solved!

[Benjamin Walkenhorst]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello again,

I think, I might have found a solution to the problem, or rather an 
explanation, as the problem doesn't go away: FreeBSD's / is ufs2, while /home 
is ufs.
/home is read just fine, but in /, mc gives me all kind of weird errors, 
displaying folders as files or not displaying them at all... I do get lots of 
kernel errors, actually.
So I guess, Linux's read-support for ufs2 isn't that great, right? Any hints 
if this might change in the near future? (FreeBSD is open-source, after 
all...)

Kind regards,

Benjamin

- --
"Der Hoffnung beraubt sein,
 heiflt noch nicht - verzweifeln."
(Albert Camus)


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Public Key available at http://www.krylon.de

iD8DBQE/EXDZoYumWdMvhMQRAt4oAJ0VKg/BWqOlDvph3MvN/i3XDsRUbwCdH6cg
kqKESy1E9p9sHpq1yNzMD/w=
=mhnL
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html