public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS & LVM: unexpected cp when issuing mv
Date: Mon, 30 Nov 2009 14:42:20 +0100	[thread overview]
Message-ID: <200911301442.20807@zmi.at> (raw)
In-Reply-To: <20091129232716.GC30608@discord.disaster>


[-- Attachment #1.1: Type: Text/Plain, Size: 1319 bytes --]

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
> normal.
 
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. :-(

mfg zmi
-- 
// 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

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-11-30 13:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-29 13:52 XFS & LVM: unexpected cp when issuing mv Michael Monnerie
2009-11-29 14:41 ` Asdo
2009-11-30 13:32   ` Michael Monnerie
2009-11-29 23:27 ` Dave Chinner
2009-11-30 13:42   ` Michael Monnerie [this message]
2009-11-30 14:21     ` Alex Elder
2009-11-30 15:30       ` Michael Monnerie
2009-12-01  0:19     ` Dave Chinner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200911301442.20807@zmi.at \
    --to=michael.monnerie@is.it-management.at \
    --cc=david@fromorbit.com \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox