Unsolved

This post is more than 5 years old

4 Posts

904

August 3rd, 2009 11:00

Differences between FA and SA flags on symdev

Hi I need your help in order to know why a device got WD on all its directors:

This is what happened:

We issued the following commands:

symdev -sid XXXX -file ./devs_to_remove_from_8cB_9cB.out write_disable -fa 8c -p 1

symdev -sid XXXX -file ./devs_to_remove_from_8cB_9cB.out write_disable -fa 9c -p 1

As you can see, we used the "FA" flag instead of the "SA" flag.

The command didn't return any errors, and actually it did what we needed. But we got one device (on a list of 79 devices), that got WD in all its directors.

Obviously the first assumption was that the wrong flag did it, but if that's the case, why none of the other devices was affected like this one?

Thanks
Alex

4 Operator

 • 

2.8K Posts

August 4th, 2009 01:00

Alex first of all welcome to our support forums .. If you have 5 minutes, go straight to our Coffee Break and introduce yourself :D

Can you please show output of the following command for one of affected devices ??

symdev -sid XXX show YYY

111 Posts

August 4th, 2009 06:00

My experience with symdev command taught me the it doesn't like the fa switch, but rather insists that I use the sa flag.
What symcli version are you running?

4 Operator

 • 

2.8K Posts

August 5th, 2009 06:00

Maxim unfortunatly I don't have S.E. installed on my laptop ;-)

Any brand new bug waiting for a fix ?? :D

111 Posts

August 6th, 2009 01:00

Actually last week I opened a case about v7 :)
when using server-client topology with 7 being the client on a win host, all symdev commands and symmask refresh don't work... :)

9 Legend

 • 

20.4K Posts

August 6th, 2009 20:00

Any brand new bug waiting for a fix ?? :D


i have one, in 6.5.3 you can not perform VDEV restore to alternate device, works fine in 7

2 Intern

 • 

1.3K Posts

August 8th, 2009 04:00

cant that one device be already on WD ?
No Events found!

Top