Jeremy,

There was a bug in s10u2 (nv bugid 6410488).
http://bugs.opensolaris.org/view_bug.do?bug_id=6410488

I believe this was the same situation you met, inusecheck error if not using canonical disk name. This has been fixed in snv42 and s10u3_b4. Patch 118997-10(x86) contains the fix.

--Larry

[EMAIL PROTECTED] wrote:

Hi everyone,


I have a question for everybody. I am using an Opteron (x4100) with solaris 10 update 2. This machine is connected to a Clarion (Cx3-80).

I use the emlxs driver and Powerpath to acces my LUNS.

Each time a allocate a new LUN, I have to Label it but the first the system sees the LUN I have the following output:

[EMAIL PROTECTED]: ~ > format emcpower37g

emcpower37g: configured with capacity of 1145.00GB
selecting emcpower37g
[disk formatted]
Error occurred with device in use checking: No such device


FORMAT MENU:
        disk       - select a disk
        type       - select (define) a disk type
        partition  - select (define) a partition table
        current    - describe the current disk
        format     - format and analyze the disk
        fdisk      - run the fdisk program
        repair     - repair a defective sector
        label      - write label to the disk
        analyze    - surface analysis
        defect     - defect list management
        backup     - search for backup labels
        verify     - read and display labels
        inquiry    - show vendor, product and revision
        volname    - set 8-character volume name
        !<cmd>     - execute <cmd>, then return
        quit
format> p


PARTITION MENU:
        0      - change `0' partition
        1      - change `1' partition
        2      - change `2' partition
        3      - change `3' partition
        4      - change `4' partition
        5      - change `5' partition
        6      - change `6' partition
        select - select a predefined table
        modify - modify a predefined partition table
        name   - name the current table
        print  - display the current table
        label  - write partition map and label to the disk
        !<cmd> - execute <cmd>, then return
        quit
partition> p
Current partition table (original):
Total disk sectors available: 2401222621 + 16384 (reserved sectors)

Part      Tag    Flag     First Sector          Size          Last Sector
0 root wm 34 128.00MB 262177 1 swap wu 262178 128.00MB 524321 2 unassigned wu 0 0 0 3 unassigned wm 0 0 0 4 unassigned wm 0 0 0 5 unassigned wm 0 0 0 6 usr wm 524322 1.12TB 2401222620 8 reserved wu 2401222621 8.00MB 2401239004
Then I recreated the partition and want to label it:

partition> p
Current partition table (unnamed):
Total disk sectors available: 2407124701 + 16384 (reserved sectors)

Part      Tag    Flag     First Sector          Size          Last Sector
0 root wm 34 1.12TB 2407124700 1 unassigned wu 0 0 0 2 unassigned wu 0 0 0 3 unassigned wm 0 0 0 4 unassigned wm 0 0 0 5 unassigned wm 0 0 0 6 unassigned wm 0 0 0 8 reserved wu 2407124701 8.00MB 2407141084
partition> lab yes
Error occurred with device in use checking: No such device
Ready to label disk, continue? yes

partition>

I wonder why I have the following error? Is it normal?

Thx
This message and any attachments (the "message") is
intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified.
                ---------------------------------------------

Ce message et toutes les pieces jointes (ci-apres le "message") sont etablis a l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le detruire et d'en avertir immediatement l'expediteur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'internet ne permettant pas d'assurer l'integrite de ce message, BNP PARIBAS (et ses filiales) decline(nt) toute responsabilite au titre de ce message, dans l'hypothese ou il aurait ete modifie.

------------------------------------------------------------------------

_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss

Reply via email to