Floppy problems using volume manager on SS20?

Floppy problems using volume manager on SS20?

Post by Jeffrey M. Smi » Sat, 23 Jul 1994 11:02:52

Anyone else having problems with the auto mount feature of floppies using
vold?  Cdrom's seem to mount ok but when a floppy is put into the floppy
drive it doesn't mount.  That is until the user types "eject floppy".  Then
it returns an error code that the device is in use and mounts it on /floppy.
Is there a fix for this or do I have something Mis-configured?

System Setup:
SparcStation 20 (1 processor) w/32megs ram.
        535 Meg HD, running Solaris 2.3 Hardware-5/94 straight install.
        FLoppy, CDROM (both Sun).

Thanks for any information,
                                                    Jeffrey Smith


Floppy problems using volume manager on SS20?

Post by Fletcher Gle » Sun, 24 Jul 1994 00:52:32

The floppy drive system has no means for detecting the insertion of
a diskette.  You must use the "volcheck" command after inserting
a diskette into the drive.


Floppy problems using volume manager on SS20?

Post by Henry Leparsk » Sun, 24 Jul 1994 04:40:42

        On our SS10/42 we have no problem in getting 'vold'
to mount the floppy on /floppy/floppy0.

The only annoyance is that a 'volcheck' from the console opens
up the volume manager on someones X terminal! We have the latest utmpd
patches, but this may not be related.


Dept. of Astronomy              phone: 519 661-2111 ext. 8697
Univ. of Western Ontario        fax:   519 661-2009
London, ON, N6A 3K7


1. Using DiskSuite ufs logging on Volume Manager logical volumes?


I am wondering if it is possible to use the ufs logging feature of
DiskSuite 4.1 on logical volumes defined by Sun Enterprise Volume
Manager 2.5, on a Solaris 2.6 system. I tried it with

# ./metainit d0 -t /dev/vx/dsk/rootdg/vol10 /dev/vx/dsk/rootdg/vol11
metainit: sun: /dev/vx/dsk/rootdg/vol10: Invalid argument

Just on the off chance that it is looking for slices with generic
c*t*d*s* names, I made symlinks to the logical volume files in the
/dev/dsk directory, and some other error came up

# ./metainit d0 -t c10t0d0s1 c10t0d0s0
metainit: sun: c10t0d0s1: already used in d0

So is there something fundamental that prevents setting up DiskSuite
trans metadevices (for ufs logging) using logical volumes? Or could it
be persuaded to work together? Are there alternatives for a logging
(journalling) filesystem aside from the following:

1. Get VxFS: too expensive.
2. Upgrade to Solaris 2.7+: need to support untested legacy
3. Get rid of Volume Manager and use DiskSuite to manage the disk array:
a lot of work here to backup data, define RAID metadevices and restore
data. Also slight loss of flexibility with the limit on slices.

Thank you very much for your suggestions.

Ed Young

Sent via Deja.com http://www.deja.com/
Before you buy.

2. I am having a problem with sort on a solaris 2.6 box using ksh

3. Mounting Volume Manager File Systems without the Volume Manager software

4. Sound support for mac68k

5. Difference between veritas volume manager and Sun StorEdge volume manager?

6. printer/scanner recommendation

7. Upgrade from Solaris 2.6 with Volume Manager 2.6 to Solaris 8 with Volume Manager 3.2

8. Int to String function

9. Sun Volume Manager/Veritas Volume Manager

10. (Issue) Upgrade from Sun Enterprise Volume Manager to Veritas Volume Manager

11. Solaris 9 volume manager OR Veritas volume manager ?

12. Solaris9 Volume Manager Vs Veritas Volume Manager

13. Veritas Volume Manager vs Sun Volume Manager