From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Cc: Ivan.Novick@emc.com
Subject: Re: inode64 mount option added after data exists
Date: Tue, 14 Dec 2010 08:19:57 +0100 [thread overview]
Message-ID: <201012140819.58723@zmi.at> (raw)
In-Reply-To: <20101214044355.GB16267@dastard>
[-- Attachment #1.1: Type: Text/Plain, Size: 905 bytes --]
On Dienstag, 14. Dezember 2010 Dave Chinner wrote:
> > Will it still work as intended in this case (use 64 bit inodes)?
>
> Yes, for newly created inodes and data.
When you have the existing files/dirs, would it help to take an existing
dir "$path/old", create a new dir "$path/new", and then do
cd $path/old
find . -type f -exec "ln {} ../new/" \;
rm *
mv ../new/* .
to get the inodes created in the new space? This could be necessary in
case the first 1TB is full, and no more inodes can be created. I'm just
not sure if that would be enough.
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531
// ****** Radiointerview zum Thema Spam ******
// http://www.it-podcast.at/archiv.html#podcast-100716
//
// Haus zu verkaufen: http://zmi.at/langegg/
[-- 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
prev parent reply other threads:[~2010-12-14 7:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 22:24 inode64 mount option added after data exists Ivan.Novick
2010-12-14 4:43 ` Dave Chinner
2010-12-14 7:19 ` Michael Monnerie [this message]
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=201012140819.58723@zmi.at \
--to=michael.monnerie@is.it-management.at \
--cc=Ivan.Novick@emc.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