* inode64 mount option added after data exists
@ 2010-12-13 22:24 Ivan.Novick
2010-12-14 4:43 ` Dave Chinner
0 siblings, 1 reply; 3+ messages in thread
From: Ivan.Novick @ 2010-12-13 22:24 UTC (permalink / raw)
To: xfs
Hi all,
Quick question about the inode64 mount option.
Is it safe to add this mount option to a file system that was already created and wrote lots of data without it.
Will it still work as intended in this case (use 64 bit inodes)?
Cheers,
Ivan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: inode64 mount option added after data exists
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
0 siblings, 1 reply; 3+ messages in thread
From: Dave Chinner @ 2010-12-14 4:43 UTC (permalink / raw)
To: Ivan.Novick; +Cc: xfs
On Mon, Dec 13, 2010 at 05:24:46PM -0500, Ivan.Novick@emc.com wrote:
> Hi all,
>
> Quick question about the inode64 mount option.
>
> Is it safe to add this mount option to a file system that was
> already created and wrote lots of data without it.
Yes.
> Will it still work as intended in this case (use 64 bit inodes)?
Yes, for newly created inodes and data.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: inode64 mount option added after data exists
2010-12-14 4:43 ` Dave Chinner
@ 2010-12-14 7:19 ` Michael Monnerie
0 siblings, 0 replies; 3+ messages in thread
From: Michael Monnerie @ 2010-12-14 7:19 UTC (permalink / raw)
To: xfs; +Cc: Ivan.Novick
[-- 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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-12-14 7:18 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox