Login or Register to Ask a Question and Join Our Community


Solaris

metadevice problem

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems Solaris metadevice problem
# 1  
Old 05-08-2010
Data metadevice problem
hi all

i am very new to solaris...i am trying configure raid 0 in my ultrascsi box which is having 6 sun36GB hard disks. I have created 4 state database replicas in the following slices /dev/dsk/c1t1d0s7 /dev/dsk/c1t2d0s7 /dev/dsk/c1t3d0s7 and /dev/dsk/c1t4d0s7. i could not use any other slices in this controller to create a mirror. when i give
# metainit d10 1 1 c1t3d0s6 ( this is a 33 GB slice in the hard disk) it says
metainit: u15_9: c1t3d0s6: overlaps with device in metadevice state database. The same thing happening on other targets (t1, t2 and t4) too. Where i am wrong...i could not trace not the problem. I need someone's help.

Sorry for my english if u feel it is bad. i am using solaris 5.10..SPARC IIe architecture.

Regards

Kingston
# 2  
Old 05-08-2010
Quote:
Originally Posted by kingston
hi all

i am very new to solaris...i am trying configure raid 0 in my ultrascsi box which is having 6 sun36GB hard disks. I have created 4 state database replicas in the following slices /dev/dsk/c1t1d0s7 /dev/dsk/c1t2d0s7 /dev/dsk/c1t3d0s7 and /dev/dsk/c1t4d0s7. i could not use any other slices in this controller to create a mirror. when i give
# metainit d10 1 1 c1t3d0s6 ( this is a 33 GB slice in the hard disk) it says
metainit: u15_9: c1t3d0s6: overlaps with device in metadevice state database. The same thing happening on other targets (t1, t2 and t4) too. Where i am wrong...i could not trace not the problem. I need someone's help.

Sorry for my english if u feel it is bad. i am using solaris 5.10..SPARC IIe architecture.

Regards

Kingston

Please post the out-put of :

1) format command and complete partition layout for c1t1d0 disk.

May be you have partitioned it wrongly...

Smilie
# 3  
Old 05-08-2010
thanks for ur quick reply....i re-partitioned all of my hard disk (obviously except root)...i outof six, four of my hdd having single partitions...say c1t1d0s7, c1t2d0s7,c1t3d0s7 and c1t4d0s7 with 33GB size. I created state replica database on all these slices and i configured mirroring too.(using c1t1d0s7 and c1t2d0s7)..it didnt give any overlapping error...Really i dont know what i am doing..Can you clarify the follwing questions.

1. is it possible to create State replica database on other slices which will not be used as volumes?
2. if it is possible what could be the size?
3. Earlierly i create two slices per hard disk c1t3d0s6 with 33.00 GB c1t3d0s7 with 50.78 MB. i created slices in slice 7 and slice 6 is for my mirroring. I did the same thing with target 4 hard disk.
what is the mistake in this?

Regards

Kingston S
# 4  
Old 05-08-2010
Quote:
Originally Posted by kingston
thanks for ur quick reply....i re-partitioned all of my hard disk (obviously except root)...i outof six, four of my hdd having single partitions...say c1t1d0s7, c1t2d0s7,c1t3d0s7 and c1t4d0s7 with 33GB size. I created state replica database on all these slices and i configured mirroring too.(using c1t1d0s7 and c1t2d0s7)..it didnt give any overlapping error...Really i dont know what i am doing..Can you clarify the follwing questions.

1. is it possible to create State replica database on other slices which will not be used as volumes?
2. if it is possible what could be the size?
3. Earlierly i create two slices per hard disk c1t3d0s6 with 33.00 GB c1t3d0s7 with 50.78 MB. i created slices in slice 7 and slice 6 is for my mirroring. I did the same thing with target 4 hard disk.
what is the mistake in this?

Regards

Kingston S

Code:
1. is it possible to create State replica database on other slices which will not be used as volumes?

YES you can use.

Code:
2. if it is possible what could be the size?

By default, the size of a state database replica is 4 Mbytes or 8192 blocks. You should create state database replicas on a dedicated slice with at least 4 Mbytes per replica. Because your disk slices might not be that small, you might want to resize a slice to hold the state database replica.


Code:
3. Earlierly i create two slices per hard disk c1t3d0s6 with 33.00 GB c1t3d0s7 with 50.78 MB. i created slices in slice 7 and slice 6 is for my mirroring. I did the same thing with target 4 hard disk.
what is the mistake in this?

Its hard to guess anything without analysing the output of some commands :
1) Please check wether slices created by you is having any overlapping cylinders or not.THEY SHOULD NOT...
2)Rest all other process is correct.You can create state database and a metadevice on single slice.
3)Please post all the commands and steps performed by you to get better idea.

Thanks,
P. S.

Smilie
Last edited by Reboot; 05-08-2010 at 08:50 AM.. Reason: typo..
# 5  
Old 05-10-2010
hi reboot
thanks for the quick reply...

how to check the slices whether its has overlaping cylinders or not?
Thanks for ur help...here is the details you asked...

Now, i delete the mirroring in my disks and get back to the eariler stage where i am getting problem to post the format output command.

1. This is the partition table in my first hard disk.

Code:
bash-3.00# format
Searching for disks...done


AVAILABLE DISK SELECTIONS:
       0. c0t0d0 <ST380011A cyl 38307 alt 2 hd 16 sec 255>
          /pci@1f,0/ide@d/dad@0,0
       1. c1t1d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
          /pci@1f,0/pci@5/pci@0/scsi@5/sd@1,0
       2. c1t2d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
          /pci@1f,0/pci@5/pci@0/scsi@5/sd@2,0
       3. c1t3d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
          /pci@1f,0/pci@5/pci@0/scsi@5/sd@3,0
       4. c1t4d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
          /pci@1f,0/pci@5/pci@0/scsi@5/sd@4,0
       5. c1t5d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
          /pci@1f,0/pci@5/pci@0/scsi@5/sd@5,0
       6. c1t6d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
          /pci@1f,0/pci@5/pci@0/scsi@5/sd@6,0
Specify disk (enter its number): 1
selecting c1t1d0
[disk formatted]

partition> 7
Part      Tag    Flag     Cylinders         Size            Blocks
  7 unassigned    wm       0 - 23955       33.00GB    (23956/0/0) 69208884

Enter partition id tag[unassigned]:
Enter partition permission flags[wm]:
Enter new starting cyl[0]:
Enter partition size[69208884b, 23956c, 23955e, 33793.40mb, 33.00gb]: 50.00mb
partition> 6
Part      Tag    Flag     Cylinders         Size            Blocks
  6 unassigned    wm       0                0         (0/0/0)            0

Enter partition id tag[unassigned]:
Enter partition permission flags[wm]:
Enter new starting cyl[0]:
Enter partition size[0b, 0c, 0e, 0.00mb, 0.00gb]: 33.00gb
partition> print
Current partition table (unnamed):
Total disk cylinders available: 24620 + 2 (reserved cylinders)

Part      Tag    Flag     Cylinders         Size            Blocks
  0 unassigned    wm       0                0         (0/0/0)            0
  1 unassigned    wm       0                0         (0/0/0)            0
  2     backup    wu       0 - 24619       33.92GB    (24620/0/0) 71127180
  3 unassigned    wu       0                0         (0/0/0)            0
  4 unassigned    wm       0                0         (0/0/0)            0
  5 unassigned    wm       0                0         (0/0/0)            0
  6 unassigned    wm       0 - 23955       33.00GB    (23956/0/0) 69208884
  7 unassigned    wm       0 -    35       50.78MB    (36/0/0)      104004

partition> label
Ready to label disk, continue? y

2. This is for my second hard disk
Code:
partition> print
Current partition table (original):
Total disk cylinders available: 24620 + 2 (reserved cylinders)

Part      Tag    Flag     Cylinders         Size            Blocks
  0 unassigned    wm       0                0         (0/0/0)            0
  1 unassigned    wm       0                0         (0/0/0)            0
  2     backup    wu       0 - 24619       33.92GB    (24620/0/0) 71127180
  3 unassigned    wu       0                0         (0/0/0)            0
  4 unassigned    wm       0                0         (0/0/0)            0
  5 unassigned    wm       0                0         (0/0/0)            0
  6 unassigned    wm       0                0         (0/0/0)            0
  7 unassigned    wm       0 - 23955       33.00GB    (23956/0/0) 69208884

partition> 7
Part      Tag    Flag     Cylinders         Size            Blocks
  7 unassigned    wm       0 - 23955       33.00GB    (23956/0/0) 69208884

Enter partition id tag[unassigned]:
Enter partition permission flags[wm]:
Enter new starting cyl[0]:
Enter partition size[69208884b, 23956c, 23955e, 33793.40mb, 33.00gb]: 50.00mb
partition> print
Current partition table (unnamed):
Total disk cylinders available: 24620 + 2 (reserved cylinders)

Part      Tag    Flag     Cylinders         Size            Blocks
  0 unassigned    wm       0                0         (0/0/0)            0
  1 unassigned    wm       0                0         (0/0/0)            0
  2     backup    wu       0 - 24619       33.92GB    (24620/0/0) 71127180
  3 unassigned    wu       0                0         (0/0/0)            0
  4 unassigned    wm       0                0         (0/0/0)            0
  5 unassigned    wm       0                0         (0/0/0)            0
  6 unassigned    wm       0                0         (0/0/0)            0
  7 unassigned    wm       0 -    35       50.78MB    (36/0/0)      104004

partition> 6
Part      Tag    Flag     Cylinders         Size            Blocks
  6 unassigned    wm       0                0         (0/0/0)            0

Enter partition id tag[unassigned]:
Enter partition permission flags[wm]:
Enter new starting cyl[0]:
Enter partition size[0b, 0c, 0e, 0.00mb, 0.00gb]: 33.00gb
partition> print
Current partition table (unnamed):
Total disk cylinders available: 24620 + 2 (reserved cylinders)

Part      Tag    Flag     Cylinders         Size            Blocks
  0 unassigned    wm       0                0         (0/0/0)            0
  1 unassigned    wm       0                0         (0/0/0)            0
  2     backup    wu       0 - 24619       33.92GB    (24620/0/0) 71127180
  3 unassigned    wu       0                0         (0/0/0)            0
  4 unassigned    wm       0                0         (0/0/0)            0
  5 unassigned    wm       0                0         (0/0/0)            0
  6 unassigned    wm       0 - 23955       33.00GB    (23956/0/0) 69208884
  7 unassigned    wm       0 -    35       50.78MB    (36/0/0)      104004

partition> label
Ready to label disk, continue? y

3. My meta databases are here
Code:
bash-3.00# metadb -a c1t1d0s7 c1t2d0s7
bash-3.00# metadb
        flags           first blk       block count
     a        u         16              8192            /dev/dsk/c1t1d0s7
     a        u         16              8192            /dev/dsk/c1t2d0s7

4. Here is the error what i am getting.

Code:
bash-3.00# metainit d10 1 1 c1t1d0s6
metainit: u15_9: c1t1d0s6: overlaps with device in metadevice state database

So Now tell me where did i made the mistake...I want to ask you one more question.
How to delete a partiton properly from format utility?

Regards


Kingston S
Moderator's Comments:
Mod Comment Please use code tags for readability, especially if a lot of command output is posted
Last edited by kingston; 05-10-2010 at 08:51 AM.. Reason: sentence mistake
# 6  
Old 05-10-2010
So, I can see that you have not partitioned the slices correctly.They are overlapping :

Code:
 
FIRST DISK : c1t1d0
 
Current partition table (unnamed):
Total disk cylinders available: 24620 + 2 (reserved cylinders)

Part      Tag    Flag     Cylinders         Size            Blocks
  0 unassigned    wm       0                0         (0/0/0)            0
  1 unassigned    wm       0                0         (0/0/0)            0
  2     backup    wu       0 - 24619       33.92GB    (24620/0/0) 71127180
  3 unassigned    wu       0                0         (0/0/0)            0
  4 unassigned    wm       0                0         (0/0/0)            0
  5 unassigned    wm       0                0         (0/0/0)            0
  6 unassigned    wm       0 - 23955       33.00GB    (23956/0/0) 69208884
  7 unassigned    wm       0 -    35       50.78MB    (36/0/0)      104004

partition> label
Ready to label disk, continue? y

Code:
So Now tell me where did i made the mistake...

As you can see 7th slice starts with cylinder-0 and ends with cylinder-35.So, 6th slice should start with cylinder-36 and end with cylinder-23955.Which is not their in your case.So, make it correct.

Same is the case with SECOND DISK.


Code:
How to delete a partiton properly from format utility?

In you case, if I am not wrong you want :
7th slice --->> 50.78MB
6th slice --->> 33.00GB

SO, you can do following :

Code:
For 7th slice :
Enter partition id tag[unassigned]:
Enter partition permission flags[wm]:
Enter new starting cyl[0]:
Enter partition size[0b, 0c, 0e, 0.00mb, 0.00gb]: 50.00mb
partition> label

Code:
For 6th slice :
Enter partition id tag[unassigned]:
Enter partition permission flags[wm]:
Enter new starting cyl[0]:36               ----->>> Notice this.
Enter partition size[0b, 0c, 0e, 0.00mb, 0.00gb]: 33.00gb
partition> label

Smilie
This User Gave Thanks to Reboot For This Post:
kingston
# 7  
Old 05-11-2010
thanks a lot...its a small but very important thing. In linux, fdisk will come with the proper cylinder number whenever we are adding or creating a partition. I need to change my mindset. Anyway thanks a lot reboot, it works fine after i partitioned correctly without any overlapping.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

Metadevice Too Small To Attach

Hi All, I am having trouble with my metadevices and I hope someone can help. when i try to attach my submirror i get the following error: root@xxxx>metattach d31 d21 metattach: tbair1: d21: submirror too small to attach root@xxxx> However, There is a submirror on the other disk which is... (3 Replies)
Discussion started by: A-Train
3 Replies

2. Solaris

Problem to understand METADEVICE and related commands

Hi everyone, I'm new with solaris administration. I have just discovered the notion of METADEVICE and I really don't understand it. Can any one please explain it to me or give me useful link ? I also want to know more about these commandes: metainit metadb metaattach Thank you ... (1 Reply)
Discussion started by: adilyos
1 Replies

3. UNIX for Dummies Questions & Answers

Can I reboot during a metadevice resync?

In my infinite lack of wisdom, I brought a Solaris 10(Sparc, 64 bit ) system down to init 1, detached a metadrive so that I could run format->analyze->refresh on it, and then reinit'd and reattached it . It started syncing the drive as it's a submirror of a mirrored drive, which happens... (8 Replies)
Discussion started by: the.gooch
8 Replies

4. Solaris

Restoring a Root File System that was on a metadevice

Hello I use Solaris 10. I need to restore the root file system, but I don't know how . i can only boot the server in safe mode or with the cd (ok boot cdrom -s) Do you guys know a good procedure, I don't want to break the mirrors. ( the server is not a cluster). Its an emergency, i would... (4 Replies)
Discussion started by: feg
4 Replies

5. Solaris

Replacement of metadevice with soft partitions

Hi guys, currently I'm working on one problem. I have Sol10 box where I need to replace old storage for the new one with minimal downtime. Layout of metadevice looks like this: d103 p 1.0GB d100 d102 p 2.0GB d100 d101 p 1.0GB d100 d100 s ... (3 Replies)
Discussion started by: brusell
3 Replies

6. Solaris

metadevice submirrors 0 and 1 not consistent

At a new job, I've inherited a handful of Solaris 10 SunFire V240 servers. I noticed that the metadevices are not consistent, in a way that I've not seen before.... internal mirrored disks: metadevice d60 has c1t0d0s6 as submirror 0 (d61) and c1t1d0s6 as submirror 1 (d62) metadevice... (1 Reply)
Discussion started by: Max Power
1 Replies

7. Solaris

Unable to mount Metadevice

Hi, I am running Solaris 8 on a V880 which has recently crashed. It has got a fibre connection to a StorageTrek array containing my database info. Since the crash I have been unable to mount the 2 metadevices which correspond to /spool & /apps - these FS's contain my db info and theredore I... (20 Replies)
Discussion started by: Duffs
20 Replies

8. Shell Programming and Scripting

Negate alerting for particular metadevice.

Hi All... I have a script that checks for any problems(particularly looks for 'Needs Maintenance') with metadevices and alerts accordingly. This was not configured to alert for a particular metadevice. Now i want to negate alerting for a particular metadevice(say d40). Is this possible? I am... (6 Replies)
Discussion started by: reddybs
6 Replies

9. Solaris

increase metadevice size

Hi, I am having two metadevices d50 and d100 which are used to created soft partitions as and when required. d50 and d100 are metadevices formed on different disks. d50 -- disks 0 & 1 d100 -- disks 2 & 3 I have a soft partition d70 os 50 GB on d50. Now there is no free space on d50. ... (1 Reply)
Discussion started by: sag71155
1 Replies

10. Solaris

insufficient metadevice database replicas ERROR

First I would like to thank this forum for assisting me in setting up my 1st sunbox. Could not have done it if it had not been for you guys and google :D I have mirrored my box and have SUCCESSFULLY tested booting from the rootdisk and rootmirror successfully. I am now looking at configuring... (2 Replies)
Discussion started by: mr_manny
2 Replies
Login or Register to Ask a Question