Maybe I’m missing something here, but a qtree is just a directory and as long as the gazillions of files are not directly inside the qtree, just copy the qtree over and mount the volume via NFS and move the files one directory up, then delete the qtree (no more files left in there).

Moving files should be very fast and then you don’t have this exception anymore… but I could just have misunderstood you, so if that’s the case, sorry for that.

Best,

Alexander Griesser

Head of Systems Operations

ANEXIA Internetdienstleistungs GmbH

E-Mail: ag@anexia.at

Web: http://www.anexia.at

Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt

Geschäftsführer: Alexander Windbichler

Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601

Von: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] Im Auftrag von Basil
Gesendet: Dienstag, 13. Jänner 2015 21:22
An: toasters@teaparty.net
Betreff: Re: Is it possible to copy a qtree to its own volume?

There's nothing wrong with it in that it'll work, but if there's a way I can make this look the same as a newly created share instead of making it yet another exception to the standard, I'd take it.

@Richard: we have a bunch of old qtree shares from the early days of this box that share a flexvol in a 32 bit aggregate. We can't upgrade to 64 bit aggregates on this box, there's no room left in the 32 bit aggregate (and it can't be increased any more), and the volume is now taking 3 days to do a backup. We're taking the highest growth and highest current sized shares and putting them into their own volumes in new aggregates with plenty of headroom.

On Tue, Jan 13, 2015 at 2:45 PM, Payne, Richard <richard.payne@amd.com> wrote:

Not a solution, but why do you want the data outside a qtree?

--rdp

From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Basil
Sent: Tuesday, January 13, 2015 2:35 PM
To: toasters@teaparty.net
Subject: Is it possible to copy a qtree to its own volume?

I'm trying to take a qtree and move it into its own flexvol (7 mode). It has millions of small files, so robocopy or ndmpcopy are taking too long for the final pre-cutover sync of the migration.

So far, the best option I can come up with is to use qtree snapmirror to copy it into a qtree in a new volume and share that qtree, however this isn't clean, and qtree snapmirror still has to span the filesystem. My other considered option was to use a volume snapmirror and then delete everything but the qtree that I need to keep on the destination volume once it's been split off, however this still leaves me with a cifs share pointing to a qtree instead of a volume. At least it would be a block copy instead of a filesystem copy, though.

Anyone have any ideas?

Basil

_______________________________________________
Toasters mailing list
Toasters@teaparty.net
http://www.teaparty.net/mailman/listinfo/toasters