On Montag, 30. November 2009 Dave Chinner wrote:
> > 1) why this happens
> It happens if you move from one project directory heirarchy to
> another - rename is not allowed across project quota boundaries as
> the moved data has to be correctly attributed to the new project.
> Hence it causes a mv to do a copy/unlink by returning a EXDEV error
> to the rename.
> > 2) how I can prevent this?
> You can't if you are moving from one project to another. If you
> move within the project heirarchy, then it will be a rename as per
Shit. So I have to turn project quotas off. I can't accept the extra
load for a simple move, as there are tons of data. Maybe the projet code
could be redesigned to allow a simple move? Is it that complicated?
If I change from project to user quota - I guess the same would still
happen? If so, I have to drop quota support, and build a script to check
quotas manually. It's a pity. :-(
// Michael Monnerie, Ing.BSc ----- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net Key-ID: 1C1209B4
Description: This is a digitally signed message part.