From what I can see from the audit logs they ran "ndmpcopy
/vol/old_vol0 /vol/vol0" after they had renamed the original vol0 to old_vol0.
I checked the audit logs on the test system and they did the ndmpcopy from vol0 to new_vol0, then did the rename. Would running the ndmpcopy when the original vol0 had been renamed first affect any of the files or the copy somehow? I wouldn't expect so, but I'll have him try it again in the morning.
Jeff
On Dec 14, 2011, at 2:10 PM, Jeff Cleverley jeff.cleverley@avagotech.com wrote:
Greetings,
We have a filer (3140) running 8.0.1 and the group wanted to convert it to a 64 bit root aggregate and vol0. I let them practice on my 8.1 test box and everything went as planned. When they did it on their 8.0.1 box, all went as plan except for the assigning the root volume.
They had moved the original vol0 out of the way and renamed the new 64 bit volume to vol0. When they ran the "vol options vol0 root" command it gave the following output:
Necessary system files are not present on the volume 'vol0'. It is recommended that you copy system files from the current root volume to the new root volume using the steps outlined in System Administration Guide, chapter 'Understanding Root Volumes', section 'Changing Root Volume'. If you do not, then after reboot, the appliance will enter setup and service will be disrupted until all the setup steps (including a reinstall of system software) have been completed. Continue with set root operation (y/n)?
He answered no. We did file listings and verified all the files are in both places. There were no obvious ndmpcopy errors. The size of space used differs a little bit, but I assume the 32 vs 64 bit aggregate layouts would cause some fluff. I even had him destroy the 64 bit vol0 volume and run everything again. Same results.
Does anyone know what this is complaining about?
Thanks,
Jeff
Did they also rename "new vol0" to vol0 before running ndmpcopy? Because if path refers to non-existing volume, ndmpcopy will happily copy into the same path inside "/" - i.e. under /vol/root_volume. I just fall in that trap yesterday.
I.e. "ndmpcopy /vol/vol0 /vol/no-such-vol" will actually create /vol/vol0/vol/no-such-vol instead of complaining.
--- With best regards
Andrey Borzenkov Senior system engineer Service operations
-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Jeff Cleverley Sent: Thursday, December 15, 2011 10:29 AM To: toasters@teaparty.net Subject: Re: 64 bit root volume conversion.
From what I can see from the audit logs they ran "ndmpcopy
/vol/old_vol0 /vol/vol0" after they had renamed the original vol0 to old_vol0.
I checked the audit logs on the test system and they did the ndmpcopy from vol0 to new_vol0, then did the rename. Would running the ndmpcopy when the original vol0 had been renamed first affect any of the files or the copy somehow? I wouldn't expect so, but I'll have him try it again in the morning.
Jeff
On Dec 14, 2011, at 2:10 PM, Jeff Cleverley jeff.cleverley@avagotech.com wrote:
Greetings,
We have a filer (3140) running 8.0.1 and the group wanted to convert it to a 64 bit root aggregate and vol0. I let them practice on my 8.1 test box and everything went as planned. When they did it on their 8.0.1 box, all went as plan except for the assigning the root volume.
They had moved the original vol0 out of the way and renamed the new 64 bit volume to vol0. When they ran the "vol options vol0 root" command it gave the following output:
Necessary system files are not present on the volume 'vol0'. It is recommended that you copy system files from the current root volume to the new root volume using the steps outlined in System Administration Guide, chapter 'Understanding Root Volumes', section 'Changing Root Volume'. If you do not, then after reboot, the appliance will enter setup and service will be disrupted until all the setup steps (including a reinstall of system software) have been completed. Continue with set root operation (y/n)?
He answered no. We did file listings and verified all the files are in both places. There were no obvious ndmpcopy errors. The size of space used differs a little bit, but I assume the 32 vs 64 bit aggregate layouts would cause some fluff. I even had him destroy the 64 bit vol0 volume and run everything again. Same results.
Does anyone know what this is complaining about?
Thanks,
Jeff
Andrey,
The new volume had been renamed to vol0 prior to the ndmpcopy. We verified the data was in the new volume and ran "ll -R" on both etc directories and diffed the files. Everything was the same.
Jeff
On Thu, Dec 15, 2011 at 12:06 AM, Borzenkov, Andrey andrey.borzenkov@ts.fujitsu.com wrote:
Did they also rename "new vol0" to vol0 before running ndmpcopy? Because if path refers to non-existing volume, ndmpcopy will happily copy into the same path inside "/" - i.e. under /vol/root_volume. I just fall in that trap yesterday.
I.e. "ndmpcopy /vol/vol0 /vol/no-such-vol" will actually create /vol/vol0/vol/no-such-vol instead of complaining.
With best regards
Andrey Borzenkov Senior system engineer Service operations
-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Jeff Cleverley Sent: Thursday, December 15, 2011 10:29 AM To: toasters@teaparty.net Subject: Re: 64 bit root volume conversion.
From what I can see from the audit logs they ran "ndmpcopy
/vol/old_vol0 /vol/vol0" after they had renamed the original vol0 to old_vol0.
I checked the audit logs on the test system and they did the ndmpcopy from vol0 to new_vol0, then did the rename. Would running the ndmpcopy when the original vol0 had been renamed first affect any of the files or the copy somehow? I wouldn't expect so, but I'll have him try it again in the morning.
Jeff
On Dec 14, 2011, at 2:10 PM, Jeff Cleverley jeff.cleverley@avagotech.com wrote:
Greetings,
We have a filer (3140) running 8.0.1 and the group wanted to convert it to a 64 bit root aggregate and vol0. I let them practice on my 8.1 test box and everything went as planned. When they did it on their 8.0.1 box, all went as plan except for the assigning the root volume.
They had moved the original vol0 out of the way and renamed the new 64 bit volume to vol0. When they ran the "vol options vol0 root" command it gave the following output:
Necessary system files are not present on the volume 'vol0'. It is recommended that you copy system files from the current root volume to the new root volume using the steps outlined in System Administration Guide, chapter 'Understanding Root Volumes', section 'Changing Root Volume'. If you do not, then after reboot, the appliance will enter setup and service will be disrupted until all the setup steps (including a reinstall of system software) have been completed. Continue with set root operation (y/n)?
He answered no. We did file listings and verified all the files are in both places. There were no obvious ndmpcopy errors. The size of space used differs a little bit, but I assume the 32 vs 64 bit aggregate layouts would cause some fluff. I even had him destroy the 64 bit vol0 volume and run everything again. Same results.
Does anyone know what this is complaining about?
Thanks,
Jeff
-- Jeff Cleverley Unix Systems Administrator 4380 Ziegler Road Fort Collins, Colorado 80525 970-288-4611
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Well ... any reason to use 8.0.1 in the first place? Actual is 8.0.2P4. I moved root volume yesterday from 32 to 64 bit using ndmpcopy without issues. The only difference was that I use it per subdirectory (I made an error initially as mentioned and could not delete extra directory as filer had no CIFS or NFS licenses; so I wanted to avoid carrying over extra garbage).
--- With best regards
Andrey Borzenkov Senior system engineer Service operations
-----Original Message----- From: Jeff Cleverley [mailto:jeff.cleverley@avagotech.com] Sent: Thursday, December 15, 2011 11:48 AM To: Borzenkov, Andrey Cc: toasters@teaparty.net Subject: Re: 64 bit root volume conversion.
Andrey,
The new volume had been renamed to vol0 prior to the ndmpcopy. We verified the data was in the new volume and ran "ll -R" on both etc directories and diffed the files. Everything was the same.
Jeff
On Thu, Dec 15, 2011 at 12:06 AM, Borzenkov, Andrey andrey.borzenkov@ts.fujitsu.com wrote:
Did they also rename "new vol0" to vol0 before running ndmpcopy? Because if path refers to non-existing volume, ndmpcopy will happily copy into the same path inside "/" - i.e. under /vol/root_volume. I just fall in that trap yesterday.
I.e. "ndmpcopy /vol/vol0 /vol/no-such-vol" will actually create /vol/vol0/vol/no-such-vol instead of complaining.
With best regards
Andrey Borzenkov Senior system engineer Service operations
-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Jeff Cleverley Sent: Thursday, December 15, 2011 10:29 AM To: toasters@teaparty.net Subject: Re: 64 bit root volume conversion.
From what I can see from the audit logs they ran "ndmpcopy
/vol/old_vol0 /vol/vol0" after they had renamed the original vol0 to old_vol0.
I checked the audit logs on the test system and they did the ndmpcopy from vol0 to new_vol0, then did the rename. Would running the ndmpcopy when the original vol0 had been renamed first affect any of the files or the copy somehow? I wouldn't expect so, but I'll have him try it again in the morning.
Jeff
On Dec 14, 2011, at 2:10 PM, Jeff Cleverley jeff.cleverley@avagotech.com wrote:
Greetings,
We have a filer (3140) running 8.0.1 and the group wanted to convert it to a 64 bit root aggregate and vol0. I let them practice on my 8.1 test box and everything went as planned. When they did it on their 8.0.1 box, all went as plan except for the assigning the root volume.
They had moved the original vol0 out of the way and renamed the new 64 bit volume to vol0. When they ran the "vol options vol0 root" command it gave the following output:
Necessary system files are not present on the volume 'vol0'. It is recommended that you copy system files from the current root volume to the new root volume using the steps outlined in System Administration Guide, chapter 'Understanding Root Volumes', section 'Changing Root Volume'. If you do not, then after reboot, the appliance will enter setup and service will be disrupted until all the setup steps (including a reinstall of system software) have been completed. Continue with set root operation (y/n)?
He answered no. We did file listings and verified all the files are in both places. There were no obvious ndmpcopy errors. The size of space used differs a little bit, but I assume the 32 vs 64 bit aggregate layouts would cause some fluff. I even had him destroy the 64 bit vol0 volume and run everything again. Same results.
Does anyone know what this is complaining about?
Thanks,
Jeff
-- Jeff Cleverley Unix Systems Administrator 4380 Ziegler Road Fort Collins, Colorado 80525 970-288-4611
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
I'm traditionally in the "if it's not broke, don't fix it" category. Being an early adopter has not generally worked well for us in the past. The 8.0.1 release level works fine for most things we want it to do, except not converting the root volume apparently :-)
I'm only testing the 8.1 release because I have a NearStore that started life as a 7.2.3 system and it has a bunch of 32 bit aggregates I would like to convert and consolidate. There is no other feature that would drive me to try it out.
Jeff
On Thu, Dec 15, 2011 at 1:04 AM, Borzenkov, Andrey andrey.borzenkov@ts.fujitsu.com wrote:
Well ... any reason to use 8.0.1 in the first place? Actual is 8.0.2P4. I moved root volume yesterday from 32 to 64 bit using ndmpcopy without issues. The only difference was that I use it per subdirectory (I made an error initially as mentioned and could not delete extra directory as filer had no CIFS or NFS licenses; so I wanted to avoid carrying over extra garbage).
With best regards
Andrey Borzenkov Senior system engineer Service operations
-----Original Message----- From: Jeff Cleverley [mailto:jeff.cleverley@avagotech.com] Sent: Thursday, December 15, 2011 11:48 AM To: Borzenkov, Andrey Cc: toasters@teaparty.net Subject: Re: 64 bit root volume conversion.
Andrey,
The new volume had been renamed to vol0 prior to the ndmpcopy. We verified the data was in the new volume and ran "ll -R" on both etc directories and diffed the files. Everything was the same.
Jeff
On Thu, Dec 15, 2011 at 12:06 AM, Borzenkov, Andrey andrey.borzenkov@ts.fujitsu.com wrote:
Did they also rename "new vol0" to vol0 before running ndmpcopy? Because if path refers to non-existing volume, ndmpcopy will happily copy into the same path inside "/" - i.e. under /vol/root_volume. I just fall in that trap yesterday.
I.e. "ndmpcopy /vol/vol0 /vol/no-such-vol" will actually create /vol/vol0/vol/no-such-vol instead of complaining.
With best regards
Andrey Borzenkov Senior system engineer Service operations
-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Jeff Cleverley Sent: Thursday, December 15, 2011 10:29 AM To: toasters@teaparty.net Subject: Re: 64 bit root volume conversion.
From what I can see from the audit logs they ran "ndmpcopy
/vol/old_vol0 /vol/vol0" after they had renamed the original vol0 to old_vol0.
I checked the audit logs on the test system and they did the ndmpcopy from vol0 to new_vol0, then did the rename. Would running the ndmpcopy when the original vol0 had been renamed first affect any of the files or the copy somehow? I wouldn't expect so, but I'll have him try it again in the morning.
Jeff
On Dec 14, 2011, at 2:10 PM, Jeff Cleverley jeff.cleverley@avagotech.com wrote:
Greetings,
We have a filer (3140) running 8.0.1 and the group wanted to convert it to a 64 bit root aggregate and vol0. I let them practice on my 8.1 test box and everything went as planned. When they did it on their 8.0.1 box, all went as plan except for the assigning the root volume.
They had moved the original vol0 out of the way and renamed the new 64 bit volume to vol0. When they ran the "vol options vol0 root" command it gave the following output:
Necessary system files are not present on the volume 'vol0'. It is recommended that you copy system files from the current root volume to the new root volume using the steps outlined in System Administration Guide, chapter 'Understanding Root Volumes', section 'Changing Root Volume'. If you do not, then after reboot, the appliance will enter setup and service will be disrupted until all the setup steps (including a reinstall of system software) have been completed. Continue with set root operation (y/n)?
He answered no. We did file listings and verified all the files are in both places. There were no obvious ndmpcopy errors. The size of space used differs a little bit, but I assume the 32 vs 64 bit aggregate layouts would cause some fluff. I even had him destroy the 64 bit vol0 volume and run everything again. Same results.
Does anyone know what this is complaining about?
Thanks,
Jeff
-- Jeff Cleverley Unix Systems Administrator 4380 Ziegler Road Fort Collins, Colorado 80525 970-288-4611
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
-- Jeff Cleverley Unix Systems Administrator 4380 Ziegler Road Fort Collins, Colorado 80525 970-288-4611
If you are trying to copy the root volume you need to use the following syntax:
ndmpcopy -f /vol/old_vol0 /vol/vol0
That is the only way you can capture the system files with ndmpcopy.
Regards,
Andre M. Clark | Sr. Consulting Engineer, Team Lead | Insight Integrated Systems Tell me I will forget... Show me I may remember... Involve me I WILL UNDERSTAND!!! Start by doing what's necessary, then what's possible, and suddenly you are doing the impossible!!!
-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Jeff Cleverley Sent: Thursday, December 15, 2011 01:29 To: toasters@teaparty.net Subject: Re: 64 bit root volume conversion.
From what I can see from the audit logs they ran "ndmpcopy
/vol/old_vol0 /vol/vol0" after they had renamed the original vol0 to old_vol0.
I checked the audit logs on the test system and they did the ndmpcopy from vol0 to new_vol0, then did the rename. Would running the ndmpcopy when the original vol0 had been renamed first affect any of the files or the copy somehow? I wouldn't expect so, but I'll have him try it again in the morning.
Jeff
On Dec 14, 2011, at 2:10 PM, Jeff Cleverley jeff.cleverley@avagotech.com wrote:
Greetings,
We have a filer (3140) running 8.0.1 and the group wanted to convert it to a 64 bit root aggregate and vol0. I let them practice on my 8.1 test box and everything went as planned. When they did it on their 8.0.1 box, all went as plan except for the assigning the root volume.
They had moved the original vol0 out of the way and renamed the new 64 bit volume to vol0. When they ran the "vol options vol0 root" command it gave the following output:
Necessary system files are not present on the volume 'vol0'. It is recommended that you copy system files from the current root volume to the new root volume using the steps outlined in System Administration Guide, chapter 'Understanding Root Volumes', section 'Changing Root Volume'. If you do not, then after reboot, the appliance will enter setup and service will be disrupted until all the setup steps (including a reinstall of system software) have been completed. Continue with set root operation (y/n)?
He answered no. We did file listings and verified all the files are in both places. There were no obvious ndmpcopy errors. The size of space used differs a little bit, but I assume the 32 vs 64 bit aggregate layouts would cause some fluff. I even had him destroy the 64 bit vol0 volume and run everything again. Same results.
Does anyone know what this is complaining about?
Thanks,
Jeff
-- Jeff Cleverley Unix Systems Administrator 4380 Ziegler Road Fort Collins, Colorado 80525 970-288-4611
_______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Our New Corporate Headquarters has Moved! Our NEW Address is: 611 Anton Blvd. Suite 700 Costa Mesa, CA 92626 714-939-2300 All Phone Numbers Will Remain the Same
Hmm ... yesterday I did
ndmpcopy /vol/vol0/ha /vol/new_vol0/ha ndmpcopy /vol/vol0/etc /vol/new_vol0/etc ndmpcopy /vol/vol0/home /vol/new_vol0/home
as far as I can tell it did boot just fine off the new_vol0. It was under 8.0.2P4.
IIRC option -f is needed if want to overwrite existing /etc; if there is no /etc on destination, it is not required.
--- With best regards
Andrey Borzenkov Senior system engineer Service operations
-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Clark, Andre Sent: Thursday, December 15, 2011 11:17 AM To: Jeff Cleverley; toasters@teaparty.net Subject: RE: 64 bit root volume conversion.
If you are trying to copy the root volume you need to use the following syntax:
ndmpcopy -f /vol/old_vol0 /vol/vol0
That is the only way you can capture the system files with ndmpcopy.
Regards,
Andre M. Clark | Sr. Consulting Engineer, Team Lead | Insight Integrated Systems Tell me I will forget... Show me I may remember... Involve me I WILL UNDERSTAND!!! Start by doing what's necessary, then what's possible, and suddenly you are doing the impossible!!!
-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Jeff Cleverley Sent: Thursday, December 15, 2011 01:29 To: toasters@teaparty.net Subject: Re: 64 bit root volume conversion.
From what I can see from the audit logs they ran "ndmpcopy
/vol/old_vol0 /vol/vol0" after they had renamed the original vol0 to old_vol0.
I checked the audit logs on the test system and they did the ndmpcopy from vol0 to new_vol0, then did the rename. Would running the ndmpcopy when the original vol0 had been renamed first affect any of the files or the copy somehow? I wouldn't expect so, but I'll have him try it again in the morning.
Jeff
On Dec 14, 2011, at 2:10 PM, Jeff Cleverley jeff.cleverley@avagotech.com wrote:
Greetings,
We have a filer (3140) running 8.0.1 and the group wanted to convert it to a 64 bit root aggregate and vol0. I let them practice on my 8.1 test box and everything went as planned. When they did it on their 8.0.1 box, all went as plan except for the assigning the root volume.
They had moved the original vol0 out of the way and renamed the new 64 bit volume to vol0. When they ran the "vol options vol0 root" command it gave the following output:
Necessary system files are not present on the volume 'vol0'. It is recommended that you copy system files from the current root volume to the new root volume using the steps outlined in System Administration Guide, chapter 'Understanding Root Volumes', section 'Changing Root Volume'. If you do not, then after reboot, the appliance will enter setup and service will be disrupted until all the setup steps (including a reinstall of system software) have been completed. Continue with set root operation (y/n)?
He answered no. We did file listings and verified all the files are in both places. There were no obvious ndmpcopy errors. The size of space used differs a little bit, but I assume the 32 vs 64 bit aggregate layouts would cause some fluff. I even had him destroy the 64 bit vol0 volume and run everything again. Same results.
Does anyone know what this is complaining about?
Thanks,
Jeff
-- Jeff Cleverley Unix Systems Administrator 4380 Ziegler Road Fort Collins, Colorado 80525 970-288-4611
_______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Our New Corporate Headquarters has Moved! Our NEW Address is: 611 Anton Blvd. Suite 700 Costa Mesa, CA 92626 714-939-2300 All Phone Numbers Will Remain the Same
_______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Andre,
The "-f" option was not used on either the 8.0.1 system or the 8.1 test system. As Andrey pointed out, the "-f" is only needed if you are overwriting /etc on a root volume. In this case the ndmpcopy was done on a newly created volume that had no data in it prior to the copy so the -f was not required.
I may have them try it anyway just in case.
Thanks,
Jeff
On Thu, Dec 15, 2011 at 12:16 AM, Clark, Andre aclark@insightinvestments.com wrote:
If you are trying to copy the root volume you need to use the following syntax:
ndmpcopy -f /vol/old_vol0 /vol/vol0
That is the only way you can capture the system files with ndmpcopy.
Regards,
Andre M. Clark | Sr. Consulting Engineer, Team Lead | Insight Integrated Systems Tell me I will forget... Show me I may remember... Involve me I WILL UNDERSTAND!!! Start by doing what's necessary, then what's possible, and suddenly you are doing the impossible!!!
-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Jeff Cleverley Sent: Thursday, December 15, 2011 01:29 To: toasters@teaparty.net Subject: Re: 64 bit root volume conversion.
From what I can see from the audit logs they ran "ndmpcopy
/vol/old_vol0 /vol/vol0" after they had renamed the original vol0 to old_vol0.
I checked the audit logs on the test system and they did the ndmpcopy from vol0 to new_vol0, then did the rename. Would running the ndmpcopy when the original vol0 had been renamed first affect any of the files or the copy somehow? I wouldn't expect so, but I'll have him try it again in the morning.
Jeff
On Dec 14, 2011, at 2:10 PM, Jeff Cleverley jeff.cleverley@avagotech.com wrote:
Greetings,
We have a filer (3140) running 8.0.1 and the group wanted to convert it to a 64 bit root aggregate and vol0. I let them practice on my 8.1 test box and everything went as planned. When they did it on their 8.0.1 box, all went as plan except for the assigning the root volume.
They had moved the original vol0 out of the way and renamed the new 64 bit volume to vol0. When they ran the "vol options vol0 root" command it gave the following output:
Necessary system files are not present on the volume 'vol0'. It is recommended that you copy system files from the current root volume to the new root volume using the steps outlined in System Administration Guide, chapter 'Understanding Root Volumes', section 'Changing Root Volume'. If you do not, then after reboot, the appliance will enter setup and service will be disrupted until all the setup steps (including a reinstall of system software) have been completed. Continue with set root operation (y/n)?
He answered no. We did file listings and verified all the files are in both places. There were no obvious ndmpcopy errors. The size of space used differs a little bit, but I assume the 32 vs 64 bit aggregate layouts would cause some fluff. I even had him destroy the 64 bit vol0 volume and run everything again. Same results.
Does anyone know what this is complaining about?
Thanks,
Jeff
-- Jeff Cleverley Unix Systems Administrator 4380 Ziegler Road Fort Collins, Colorado 80525 970-288-4611
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Our New Corporate Headquarters has Moved! Our NEW Address is: 611 Anton Blvd. Suite 700 Costa Mesa, CA 92626 714-939-2300 All Phone Numbers Will Remain the Same
-
Borzenkov, Andrey -
Clark, Andre -
Jeff Cleverley