Re: accessing NetBSD filesystem

2005-12-25 Thread Anatoli Klassen

Hanspeter Roth wrote:


Fdisk shows sysid 165 (0xa5) for partition 3. This is where FreeBSD
is installed. And Fdisk shows sysid 169 (0xa9) for partition 4. This
is where NetBSD is installed.
In /dev there are ad0s3 and ad0s3[a-g] but there is only a ad0s4.
So how can filesystems of my NetBSD in ad0s4 be accessed?



AFAIK you can access only the 'a' partition of the NetBSD slice.
Just mount it.

If you need other partitions, try to use following module:

http://www.26th.net/public/projects/freebsd/geom_nbsd/geom_nbsd.tgz

1. Download, unpack, go it to the dir.
2. Say "make".
3. Sys "kldload ./geom_nbsd.ko"
4. All /dev/ad0s3[a-g] should appear.
5. Now mount all partitions as usual.

The module is tested on 6.x and CURRENT. One known bug - it's impossible 
to unload it, you have to reboot for this.

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: accessing NetBSD filesystem

2005-12-19 Thread Stefan Esser
Pawel Jakub Dawidek schrieb:
> On Sun, Dec 18, 2005 at 04:16:16PM +0100, [EMAIL PROTECTED] wrote:

> +> FFS v1 and v2 are both working. I'm using that everyday. The one part
> +> which needs attention is soft updates: FreeBSD / DragonFly have it as
> +> permanent flag, NetBSD as mount option.
> 
> Interesting. In FreeBSD fsck(8) works differently for SU-enabled FS, so
> having SU as a mount option won't be possible (if we want to protect our
> users from a foot-shooting).
> And because of the way SU works, it is possible to run background fsck,
> as the only problems are unreferenced objects (inodes, blocks, etc.).

No, I've been running with soft-updates as a mount option for years
(starting a few months after it made it into the then -current). My
patches were even accepted for later integration by Kirk McKusick after
some discussion, but there was some resistance to integrate it at that
time (wait for the next major release) and then because it had been a
tunefs option for so long and the default had been set to "on" in
sysinstall.

I'm still convinced, that my solution is better than what we currently
have, and that is the reason I keep on maintaining the patch on my local
systems.

There is no problem with fsck, since all the patch does is simulate the
effect of a tunefs -n enable/disable immediately before a r/w mount of
the partition. That means, that fsck sees the previous state of the
softdep flag (no change of the current behaviour). Even if I mount a
removable disk without soft-updates, which was not cleanly unmounted
before and had soft-updates enable, fsck will see the soft-updates flag
and treat the partition correctly. The next mount will set (but not
necessarily change) the softdep flag in the superblock depending on the
mount options in effect. That guarantees, that the drive will be
correctly checked on a system without my patch, in case that should be
required.

My patch is without any risk and pre-dates the import of soft-updates to
NetBSD (I never checked, whether they used my then long published diffs
or implemented the softdep mount option themselves).

I'd appreciate if my patch would be reviewed and possibly accepted for
-current. It affects just a few lines of code (use the mount option
instead of the flag found in the super block when mounting a drive r/w;
ignore requests to turn off softdep for a drive mounted r/w).

Regards, STefan
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: accessing NetBSD filesystem

2005-12-18 Thread Pawel Jakub Dawidek
On Sun, Dec 18, 2005 at 04:16:16PM +0100, [EMAIL PROTECTED] wrote:
+> On Sun, Dec 18, 2005 at 01:54:18AM +0100, Gilbert Fernandes wrote:
+> > 
+> > The FreeBSD UFS is the FFS accessed through the VFS layer, but basically
+> > the format is the same. If you want to have access, from FreeBSD, to
+> > NetBSD partitions, make sure the NetBSD partitions have been formated
+> > using FFSv2 which is the port of UFS to NetBSD. There are some
+> > differences though : no ACL support nor snapshots available there.
+> 
+> FFS v1 and v2 are both working. I'm using that everyday. The one part
+> which needs attention is soft updates: FreeBSD / DragonFly have it as
+> permanent flag, NetBSD as mount option.

Interesting. In FreeBSD fsck(8) works differently for SU-enabled FS, so
having SU as a mount option won't be possible (if we want to protect our
users from a foot-shooting).
And because of the way SU works, it is possible to run background fsck,
as the only problems are unreferenced objects (inodes, blocks, etc.).

-- 
Pawel Jakub Dawidek   http://www.wheel.pl
[EMAIL PROTECTED]   http://www.FreeBSD.org
FreeBSD committer Am I Evil? Yes, I Am!


pgpBMllV0FSGm.pgp
Description: PGP signature


Re: accessing NetBSD filesystem

2005-12-18 Thread joerg
On Sun, Dec 18, 2005 at 01:54:18AM +0100, Gilbert Fernandes wrote:
> 
> The FreeBSD UFS is the FFS accessed through the VFS layer, but basically
> the format is the same. If you want to have access, from FreeBSD, to
> NetBSD partitions, make sure the NetBSD partitions have been formated
> using FFSv2 which is the port of UFS to NetBSD. There are some
> differences though : no ACL support nor snapshots available there.

FFS v1 and v2 are both working. I'm using that everyday. The one part
which needs attention is soft updates: FreeBSD / DragonFly have it as
permanent flag, NetBSD as mount option.

Joerg
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: accessing NetBSD filesystem

2005-12-17 Thread Gilbert Fernandes
> FFS == UFS.

The FreeBSD UFS is the FFS accessed through the VFS layer, but basically
the format is the same. If you want to have access, from FreeBSD, to
NetBSD partitions, make sure the NetBSD partitions have been formated
using FFSv2 which is the port of UFS to NetBSD. There are some
differences though : no ACL support nor snapshots available there.

Please use NetBSD 2.x (I use 2.1 but I got a machine running current)
and format the partition to be shared using FFSv2 on NetBSD.

Should work fine.

FFSv2 (UFS2 in FreeBSD) is not the defautl type in NetBSD 2 for now. I
have not checked in current. So if you want to use newfs from NetBSD,
don't forget to ask for FFSv2 (-O 2).

FFS code in NetBSD's kernel contains the options required for UFS2
support.

There are superblock changes in FFSv2 (UFS2). So don't use old (as in
NetBSD 1.6.x) fsck on such volumes. It is possible to do an upgrade on
fsck_ffs before using FFSv2 and this works fine in 1.6.x

Please read the following doc :

http://sixshooter.v6.thrupoint.net/jeroen/faq.html

The NetBSD's current newfs man page
(http://netbsd.gw.com/cgi-bin/man-cgi?newfs++NetBSD-current) makes
mention of the ACL so perhaps they're supported in NetBSD-current :)

--
unzip ; strip ; touch ; grep ; finger ; mount ; fsck ; more ; yes ;
fsck ; umount ; sleep
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: accessing NetBSD filesystem

2005-12-17 Thread Hanspeter Roth
  On Dec 17 at 20:07, Mathieu Arnold spoke:

> +-Le 17/12/2005 18:10 +0100, Hanspeter Roth a dit :
> |   On Dec 17 at 14:42, [EMAIL PROTECTED] spoke:
> | 
> |> On Sat, Dec 17, 2005 at 01:20:06PM +0100, Hanspeter Roth wrote:
> |> > 
> |> > is it possible to access Fast Filesystems from a NetBSD installation
> |> > on the same disk?
> |> 
> |> As long as they have the same Endianess, yes. You might get some
> |> warnings about the disklabel, otherwise it should be fine.
> | 
> | How can one activate the Fast Filesystem support? Is there a kernel
> | module to load? Shouldn't the respective entries /dev/ad0s4* appear
> | provided the NetBSD installation is in /dev/ad0s4?
> 
> FFS == UFS.

Fdisk shows sysid 165 (0xa5) for partition 3. This is where FreeBSD
is installed. And Fdisk shows sysid 169 (0xa9) for partition 4. This
is where NetBSD is installed.
In /dev there are ad0s3 and ad0s3[a-g] but there is only a ad0s4.
So how can filesystems of my NetBSD in ad0s4 be accessed?

-Hanspeter
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: accessing NetBSD filesystem

2005-12-17 Thread Mathieu Arnold
+-Le 17/12/2005 18:10 +0100, Hanspeter Roth a dit :
|   On Dec 17 at 14:42, [EMAIL PROTECTED] spoke:
| 
|> On Sat, Dec 17, 2005 at 01:20:06PM +0100, Hanspeter Roth wrote:
|> > 
|> > is it possible to access Fast Filesystems from a NetBSD installation
|> > on the same disk?
|> 
|> As long as they have the same Endianess, yes. You might get some
|> warnings about the disklabel, otherwise it should be fine.
| 
| How can one activate the Fast Filesystem support? Is there a kernel
| module to load? Shouldn't the respective entries /dev/ad0s4* appear
| provided the NetBSD installation is in /dev/ad0s4?

FFS == UFS.

-- 
Mathieu Arnold
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: accessing NetBSD filesystem

2005-12-17 Thread Hanspeter Roth
  On Dec 17 at 14:42, [EMAIL PROTECTED] spoke:

> On Sat, Dec 17, 2005 at 01:20:06PM +0100, Hanspeter Roth wrote:
> > 
> > is it possible to access Fast Filesystems from a NetBSD installation
> > on the same disk?
> 
> As long as they have the same Endianess, yes. You might get some
> warnings about the disklabel, otherwise it should be fine.

How can one activate the Fast Filesystem support? Is there a kernel
module to load? Shouldn't the respective entries /dev/ad0s4* appear
provided the NetBSD installation is in /dev/ad0s4?

-Hanspeter
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: accessing NetBSD filesystem

2005-12-17 Thread joerg
On Sat, Dec 17, 2005 at 01:20:06PM +0100, Hanspeter Roth wrote:
> 
> is it possible to access Fast Filesystems from a NetBSD installation
> on the same disk?

As long as they have the same Endianess, yes. You might get some
warnings about the disklabel, otherwise it should be fine.

Joerg
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"



accessing NetBSD filesystem

2005-12-17 Thread Hanspeter Roth
Hello,

is it possible to access Fast Filesystems from a NetBSD installation
on the same disk?

-Hanspeter
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"