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

Laugardaginn, þann 6 maí 2006 11:50 skrifaði Boyd Lynn Gerber:

...

I am trying to move a client to SUSE Linux 10.0 from SCO UnixWare 7.1.4. I did the following to be able to mount a UnixWare 7 drive on my SUSE Linux 10.0 system.

[snip]

Isn't the system you are trying to mount, really an USF or SYSV file system.

I know it is VxFS as that is the default filesys for UnixWare 7. I did try USF and SYSV with same error. From http://www.linux.com/howtos/Filesystems-HOWTO-9.shtml I have mounted them before. I just can not figure out why I can not mount it now. 9.31 VxFS - Veritas filesystem (HP-UX, SCO UnixWare, Solaris) This is commercial filesystem developer by Veritas Inc. You can see it in HP-UX, SCO UnixWare, Solaris and probably other systems. It has very interesting features: Extent based allocation, Journaling, access control lists (ACLs), up to 2 terabyte large file support, online backup (snapshot filesystem), BSD style quotas and many more. Three VxFS versions are available with VxFS: Version 1: This is original VxFS, not commonly in use. Version 2: Support for filesets and dynamic inode allocation. Version 4: Latest version, supports large files and quotas. Note that HP-UX, Solaris and UnixWare versions use slightly different structures, so you may not be able to read VxFS when you connect it to different system. VxFS related links: * http://www.veritas.com/ - Veritas Inc < vx-sales@veritas.com>. http://uw714doc.sco.com/en/ODM_FSadmin/CONTENTS.html - VxFS ODM FS Admin UnixWare 7 (documentation, really good). and the prtvtoc works giving me this... slice 0: BACKUP permissions: UNMOUNTABLE VALID starting sector: 32 length: 17772512 slice 1: USR permissions: VALID starting sector: 2144 length: 17768448 slice 7: BOOT permissions: UNMOUNTABLE VALID starting sector: 32 length: 34 slice 8: ALT SEC/TRK permissions: UNMOUNTABLE VALID starting sector: 66 length: 2048 Thanks, - -- Boyd Gerber ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQFEXYmvVtBjDid73eYRAmveAJ4h84ge/797+9Rg1R8kWVVgKaqZ9wCeIG4b jjBNr0qrjIpE1HmxXKoRw/o= =wUQF -----END PGP SIGNATURE-----

When I run setleds from the CLI I get this error: linux:/home/nathan/Documents/ # setleds -L +num KDGKBLED: Invalid argument Error reading current flags setting. Maybe you are not on the console? linux:/home/nathan/Documents/repairkit # Is there something I need to configure for this command to work ? (I'm using openSuse 10.0) Thanks, Digsy Send instant messages to your online friends http://uk.messenger.yahoo.com

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

On Sunday 07 May 2006 01:46, Boyd Lynn Gerber wrote:

...

slice 8: ALT SEC/TRK permissions: UNMOUNTABLE VALID starting sector: 66 length: 2048 I've briefly scanned the links you provided and here's my decidedly non-expert opinion: I think the system feedback you're getting is accurate. I think it is telling you it 'sees' what appear to be valid partitions but they can't be mounted because support for the filesystem contained within them isn't available... not compiled into the kernel and no module loaded.

Thanks, The kernel module is freevxfs I tried # modprobe freevxfs # modprobe -l freevxfs | grep freevxfs alias vxfs freevxfs

Regarding this statement:

...

From http://www.linux.com/howtos/Filesystems-HOWTO-9.shtml I have mounted them before.  I just can not figure out why I can not mount it now.

Are you saying you've mounted these specific partitions before, or are you saying... in a generic sense... you've mounted VxFS filesystems under Linux before. You have to distinguish between supported and non-supported (by GPL'd tools) implementations of VxFS. That's kind of what this paragraph is alluding to:

I installed the kernel source for the latest kernel and did the steps mentioned in my first email. It built the freevxfs module and installed it in /lib/modules/2.6.13-15.8-default/kernel/fs/freevxfs/freevxfs.ko

Of course, I could be all wet here, but I've been doing this stuff a long time and that's how I'd interpret the data I've seen thus far.

I have mount UnixWare 7.1.4 partitions on SUSE 9.3 and 9.2. I thought I had also done it on SUSE 10.0, but the drive I used is now 10.1 RC3 so I can not recheck it. I had followed the same steps. Thanks, - -- Boyd Gerber ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQFEXlKvVtBjDid73eYRAmSCAJ0SmtpsidQtA8gMageRE0/UpZkRYACfU1RK egMrJWDp6u0Oc4IlfM1T+oo= =Sn/K -----END PGP SIGNATURE-----

Carl Hartung writes:

My comprehension of your circumstances is much clearer now, thanks. I saw (but skimmed over and I guess overlooked) you building & installing the freevxfs module at the top of your first post. ;-) Sorry.

I can't tell from your reply, though, if you're having trouble mounting filesystems on the same physical device that previously mounted under 9.2 and 9.3? Or are you attempting this under 10.1RC3 on a different device with VxFS slices on it? If the latter, do you know which version of VxFS they're written in and is that version supported by the freevxfs module at all?

To further complicate matters, even if Linux has the appropriate VxFS filesystem suport in the kernel, there is an additional hurdle that will need to be overcome. Linux's disk partitioning scheme is only via fdisk (or fdisk-like), each of the fdisk partitions could be a Linux FS, Linux swap device, Windows FS, etc. This is unlike Unixware, which further subdivides a fdisk partition into slices, so each slice can be a Unixware filesystem or swap, etc. The beginning of the the partition is not the beginning of the root VxFS filesystem's slice. There is a little VTOC descriptor that describes where and how big each of slices are, and then a small /stand filesystem where the kernel is located (of type bfs, a single-directory, always contiguous filesystem), and then a swap slice, etc., before the root VxFS fs. I don't think there is any "canned" solution to make Linux recognize the Unixware VTOC and to find the appropriate portion of the partition for the root filesystem (and possibly other filesystems) to mount. -Ti

On Sunday 07 May 2006 17:35, Boyd Lynn Gerber wrote:

The UnixWare disk is the same one I had mounted on SUSE Pro 9.3 and I think 10.0.  

Hi Boyd, I think I'm sufficiently up to speed on the symptoms, now. The 9.3 system that you were able mount the UnixWare disk on has been upgraded to 10.1 RC3 and you're no longer able to mount the UnixWare disk after following the same procedure. Can you please point me to the documentation that you used to compile the module? And please post the results of lsmod | grep vx regards, Carl

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

...

On Sunday 07 May 2006 17:35, Boyd Lynn Gerber wrote:

...

The UnixWare disk is the same one I had mounted on SUSE Pro 9.3 and I think 10.0.  

I think I'm sufficiently up to speed on the symptoms, now. The 9.3 system that you were able mount the UnixWare disk on has been upgraded to 10.1 RC3 and you're no longer able to mount the UnixWare disk after following the same procedure.

Can you please point me to the documentation that you used to compile the module?

/usr/src/linux-2.6.13-15.8/README

And a file I created on SUSE Pro 9.2 called build all_for_linux_unixware

cd /usr/src/linux-Kernal-Source/ make cloneconfig make modules_prepare make menuconfig make xconfig make make modules make install make modules_install

...

And please post the results of lsmod | grep vx

# lsmod | grep vx freevxfs 14212 0

Also in my notes make sure UNIXWARE DISKLABLE is yes. CONFIG_UNIXWARE_DISKLABEL=y and from fs/Kconfig config VXFS_FS tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible) "help FreeVxFS is a file system driver that support the VERITAS VxFS(TM) file system format. VERITAS VxFS(TM) is the standard file system of SCO UnixWare (and possibly others) and optionally available for Sunsoft Solaris, HP-UX and many other operating systems. Currently only readonly access is supported. NOTE: the file system type as used by mount(1), mount(2) and fstab(5) is 'vxfs' as it describes the file system format, not the actual driver. To compile this as a module, choose M here: the module will be called freevxfs. If unsure, say N. and from fs/partitions/Kconfig config UNIXWARE_DISKLABEL bool "Unixware slices support" depends on PARTITION_ADVANCED && MSDOS_PARTITION ---help--- Like some systems, UnixWare uses its own slice table inside a partition (VTOC - Virtual Table of Contents). Its format is incompatible with all other OSes. Saying Y here allows you to read VTOC and further mount UnixWare partitions read-only from within Linux if you have also said Y to "UFS file system support" or "System V and Coherent file system support", above. This is mainly used to carry data from a UnixWare box to your Linux box via a removable medium like magneto-optical, ZIP or removable IDE drives. Note, however, that a good portable way to transport files and directories between unixes (and even other operating systems) is given by the tar program ("man tar" or preferably "info tar"). If you don't know what all this is about, say N. - -- Boyd Gerber ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQFEXpdYVtBjDid73eYRAqUyAJwPcP348UKAKw5/KIBEtUsAKt7ojwCdG7Kl fDuSXhmb2JaWSLJTveCWh6I= =9cSN -----END PGP SIGNATURE-----

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

It looks like the module is integrating and communicating correctly with the kernel but, downstream, is unable to read the Object Location Table

Yes.

And this:

...

SCSI device sdb: 17773524 512-byte hdwr sectors (9100 MB) SCSI device sdb: drive cache: write through sdb: sdb1 sdb1:

looks to me like it's being treated as a primary partition (sdb1) containing three logical partitions (sdb5, sdb6 & sdb7)

Does this match your understanding of the filesystem and partition(s) structure from the UnixWare side?

Yes, I think. I have been out all day and just got back. I setup an other machine to test with. It have more slices and the same thing happens with it only more. I did find part of an old boot.msg and boot.omsg from 9.3 and it has the same info in it. It appears that in that version it did the same thing. Someone asked what happens without the -t vxfs... # mount /dev/sdb1 /unixware7 mount: you must specify the filesystem type - -- Boyd Gerber ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQFEYBcIVtBjDid73eYRAk1eAJ4sbYc5Lb8thNzTTqMqKRyqczUpvACfQqEn e83RyAehDIx52ZxYrYpPlRg= =FsIl -----END PGP SIGNATURE-----

On Monday 08 May 2006 09:57, Ken Schneider wrote:

And you did remember to reboot after installing the new kernel and modules, correct?

Hi Ken, For the record, the last line of the routine/script he used was:

"shutdown -g0 -y -i6"

regards, Carl

Boyd Lynn Gerber wrote:

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

...

Laugardaginn, þann 6 maí 2006 11:50 skrifaði Boyd Lynn Gerber:

...

I am trying to move a client to SUSE Linux 10.0 from SCO UnixWare 7.1.4. I did the following to be able to mount a UnixWare 7 drive on my SUSE Linux 10.0 system.

[snip]

Isn't the system you are trying to mount, really an USF or SYSV file system.

I know it is VxFS as that is the default filesys for UnixWare 7. I did try USF and SYSV with same error. From http://www.linux.com/howtos/Filesystems-HOWTO-9.shtml I have mounted them before. I just can not figure out why I can not mount it now.

<snip>

- -- Boyd Gerber

Hi-- I mount my UnixWare-2.03 vxfs slices as type "nfs" on my SuSE linux 10.0 box hth Tom Wekell

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

Boyd Lynn Gerber wrote:

...

...

Laugardaginn, þann 6 maí 2006 11:50 skrifaði Boyd Lynn Gerber:

...

I am trying to move a client to SUSE Linux 10.0 from SCO UnixWare 7.1.4. I did the following to be able to mount a UnixWare 7 drive on my SUSE Linux 10.0 system. Isn't the system you are trying to mount, really an USF or SYSV file system. I mount my UnixWare-2.03 vxfs slices as type "nfs" on my SuSE linux 10.0 box hth

What command do you use? # mount -t nfs /dev/sdb1 /unixware7 mount: directory to mount not in host:dir format Thanks, - -- Boyd Gerber ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQFEYBhsVtBjDid73eYRAqQZAKCGz9iyWdI68ybWbC5Wn16+RIMmPwCfRgh6 vxt3aA1hWEXwLPEPqaar1Kc= =uhAh -----END PGP SIGNATURE-----

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

...

I am trying to move a client to SUSE Linux 10.0 from SCO UnixWare 7.1.4. I did the following to be able to mount a UnixWare 7 drive on my SUSE Linux 10.0 system.

cd /usr/src/linux-2.6.13-15.8/ make cloneconfig make modules_prepare make menuconfig make xconfig make make modules make install make modules_install shutdown -g0 -y -i6

...

What do you get if you use: mount -r /dev/sdb1 /unixware7 Don't specify the filesystem, let the kernel figure out what is used.

# mount /dev/sdb1 /unixware7 mount: you must specify the filesystem type - -- Boyd Gerber ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQFEYBd4VtBjDid73eYRAoWYAKCF1XgEGna748rByXo9n1Rjbp4n3gCfbkDb gS8qHJ16szg6+WyQsmjKRy0= =stxy -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 9 May 2006, Carl Hartung wrote:

On Tuesday 09 May 2006 00:15, Boyd Lynn Gerber wrote:

...

# mount /dev/sdb1 /unixware7 mount: you must specify the filesystem type Did you enable VTOC support when you built the module?

Yes, I even changed the M's to Y for the other defines. CONFIG_UNIXWARE_DISKLABEL=y config UNIXWARE_DISKLABEL bool "Unixware slices support" depends on PARTITION_ADVANCED && MSDOS_PARTITION ---help--- Like some systems, UnixWare uses its own slice table inside a partition (VTOC - Virtual Table of Contents). Its format is incompatible with all other OSes. Saying Y here allows you to read VTOC and further mount UnixWare partitions read-only from within Linux if you have also said Y to "UFS file system support" or "System V and Coherent file system support", above. This is mainly used to carry data from a UnixWare box to your Linux box via a removable medium like magneto-optical, ZIP or removable IDE drives. Note, however, that a good portable way to transport files and directories between unixes (and even other operating systems) is given by the tar program ("man tar" or preferably "info tar"). - -- Boyd Gerber ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQFEYBxUVtBjDid73eYRApa5AJ9Jjb0AMjzUkLq4YnDLTY3PTViJgQCfWrAW daPljhe3bwEZWqYMNnpYP9k= =Okvc -----END PGP SIGNATURE-----

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

On Tuesday 09 May 2006 00:36, Boyd Lynn Gerber wrote:

...

Yes, I even changed the M's to Y for the other defines.

Well, I'm sure this is very frustrating to you, Boyd. It is for me, too. I think the kernel 'seeing' one unmountable primary with three unmountable logical partitions is an important clue. It sure would be nice if there were more complete documentation and/or a maintainer's mailing list archive to research.

And, given the amount of time you've invested so far on this project, it would almost be worth rebuilding the prior working 9.3 arrangement on another machine just to get the data transferred. Too bad you don't have a second 'test bench' system to do that with... or do you?

I do not have an other test bed. I went out and got a DVD burner and used backup edge. http://www.microlite.com. I installed it in the UnixWare System backed up to DVD pulled the drive and put it in the SUSE Linux box and restored the information. I am glad there are more ways to do things. I did not have access over the weekend to the system. That is why I have been out all day. Now to the work of getting everything working. Thanks to everyone for your ideas. - -- Boyd Gerber ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQFEYDA+VtBjDid73eYRAhE8AJ9eaCzRKi++BqMlVh8TlQHXdm873wCgi3aG GE8cTlCjxTrHPorg+Dh/xl4= =goIP -----END PGP SIGNATURE-----