This post is more than 5 years old

90 Posts

1813

January 25th, 2007 11:00

Problem making new NAS POOL

Ok, I'm confused! As per a previous posting, I got in a tray of SATA drives, created a couple 6+1 Raid 5 arrays, created a couple LUNS, and dropped them into my CELERRA Strorage Group. In Celerra Manager, a new system defined clarata_archive pool was created but no volumes.

From the Celerra CLI:
[nasadmin@celerra2 nasadmin]$ nas_pool -list
id inuse acl name
3 n 421 clar_r5_performance
4 y 421 clar_r5_economy
10 n 421 clarata_archive

Doing a nas_disk -l shows:
.
.
.
19 y 547418 APM00060504673-001C CLSTD d19 1,2,3,4
20 y 547418 APM00060504673-001A CLSTD d20 1,2,3,4
21 n 511999 APM00060504673-002A CLATA d21 1,2,3,4
22 n 511999 APM00060504673-0029 CLATA d22 1,2,3,4

If I try to create a user defines pool with these drives I get:
Error 3147: volume d21 resides on a reserved disk

So, how do I get these volumes in a pool I can use. I appreciate any help you can give on this.

Harold

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

January 27th, 2007 11:00

Harold,

out of curiosity, can you tell me HostID of these 2 new LUNs that you added to the storage group? Make sure their HostID is not between 0-16 as those are reserved for datamover boot luns.

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

January 25th, 2007 11:00

you dont' need to. If you use AVM (automatic volume manager), all you need to do is to create a new file system and specify pool clarata_archive as your pool, it will pull those luns in into the storage pool.

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

January 25th, 2007 13:00

can you try command line:

nas_fs -name fs47 -create size=15G pool=clarata_archive

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

January 25th, 2007 13:00

can you also post output:

nas_pool -info clarata_archive

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

January 25th, 2007 13:00

this is what mine looks like, this is a system defined pool using AVM:

[admin@cs0 admin]$ nas_pool -info clarata_archive
id = 10
name = clarata_archive
description = CLARiiON RAID5 on S-ATA
acl = 421
in_use = True
clients = fs32,fs34,fs33,fs36,fs38,fs37,fs39,fs40,fs42,fs44
members = v1034,v1038,v1041
default_slice_flag = True
is_user_defined = False
disk_type = CLATA
server_visibility = server_2,server_3,server_4,server_5,server_6
volume_profile = clarata_archive_vp
is_dynamic = True
is_greedy = True

90 Posts

January 25th, 2007 13:00

OK

[nasadmin@celerra2 nasadmin]$ nas_fs -name fs47 -create size=15G pool=clarata_archive
Error 3006: CLATA : volume(s) are not available

90 Posts

January 25th, 2007 13:00

Tried that. When I select New from the File System tab in Celerra Manager, it only shows the currently used pool, not the ATA pool.
HH

90 Posts

January 25th, 2007 14:00

Her's mine:

[nasadmin@celerra2 nasadmin]$ nas_pool -info clarata_archive
id = 10
name = clarata_archive
description = CLARiiON RAID5 on S-ATA
acl = 421
in_use = False
clients =
members =
default_slice_flag = True
is_user_defined = False
volume_profile = clarata_archive_vp
is_dynamic = True
is_greedy = True
[nasadmin@celerra2 nasadmin]$

Problem being, it's not in use because there's no members. This got created when I dropped the ATA drives into the Storage Group and I haven't been able to get drives in there. The Celerra sees the volumes, but they don't appear to have been put in the pool.
19 y 547418 APM00060504673-001C CLSTD d19 1,2,3,4
20 y 547418 APM00060504673-001A CLSTD d20 1,2,3,4
21 n 511999 APM00060504673-002A CLATA d21 1,2,3,4
22 n 511999 APM00060504673-0029 CLATA d22 1,2,3,4

Getting very frustrated!

HH

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

January 25th, 2007 14:00

have you run ?:

server_devconfig ALL -c -s -a

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

January 26th, 2007 07:00

it's safe, i run this command whenever i present new luns to data movers. This command rescans for luns and creates new devices if new luns are detected.

90 Posts

January 26th, 2007 07:00

Nope. There wasn't any reference to doing a devconfig in anything I read and am hesitant to try stuff on a production box. When I used to map Celerra drives on our old Symm I would have to run devconfig but I saw no ref to it with our new Clariion and Celerra.
So, it's safe to do this? Please forgive the paranoia, have had large chunks of my anatomy taken out trusting someone else's guesses.
Harold

90 Posts

January 26th, 2007 08:00

Ran the devconfig. No change. nas_disk -l still lists devices as unused, Celerra Manager still only displays the original pool when trying to create a new file system.
HH

90 Posts

January 26th, 2007 11:00

More info:

Running server_devconfig server_2 -l -s -d gives:

d20 c16t1l13 APM00060504673 001A
d20 c32t1l13 APM00060504673 001A
d20 c0t1l13 APM00060504673 001A
d20 c48t1l13 APM00060504673 001A
d21 c0t0l6 APM00060504673 002A
d21 c48t0l6 APM00060504673 002A
d21 c16t0l6 APM00060504673 002A
d21 c32t0l6 APM00060504673 002A
d22 c0t0l7 APM00060504673 0029
d22 c48t0l7 APM00060504673 0029
d22 c16t0l7 APM00060504673 0029
d22 c32t0l7 APM00060504673 0029

note that d21 and d22, the sata LUNs in question, have no "l" or LUN part to their addr unlike d20 etc.

HH

90 Posts

January 26th, 2007 14:00

Per the docs and a previous response on this forum, Clariion also supports 6+1 for ATA drives. At least that's the way I read it. (Managing Celerra Volumes and File Systems with AVM p.28)

HH

117 Posts

January 26th, 2007 16:00

Doing a "rescan all" in the GUI will also do the same thing.

Running the server_devconfig -create should be fine, though before you run the command just make sure that everything's okay, storage-wise - that you can see each path to the SPs, and that no LUNs are failed over. Also, don't forget to run the "devconfig" command against each datamover (or use the "ALL" option when running, to be sure all DMs see and configure the new LUNs.

0 events found

No Events found!

Top