xfs
[Top] [All Lists]

Re: deep chmod|chown -R begin to start OOMkiller

To: CHIKAMA masaki <masaki-c@xxxxxxxxxx>
Subject: Re: deep chmod|chown -R begin to start OOMkiller
From: Eric Sandeen <sandeen@xxxxxxx>
Date: Tue, 13 Dec 2005 13:05:30 -0600
Cc: David Chinner <dgc@xxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: <20051213211445.105c6ddc.masaki-c@xxxxxxxxxx>
References: <20051207183531.5c13e8c5.masaki-c@xxxxxxxxxx> <20051208070841.GJ501696@xxxxxxxxxxxxxxxxx> <20051209104148.346f2ff5.masaki-c@xxxxxxxxxx> <20051212014633.GC19154461@xxxxxxxxxxxxxxxxx> <20051212213032.7510e99e.masaki-c@xxxxxxxxxx> <20051213015514.GX501696@xxxxxxxxxxxxxxxxx> <20051213211445.105c6ddc.masaki-c@xxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.6-1.1.fc4 (X11/20050720)
CHIKAMA masaki wrote:
Ok. I understand.
But sorry, this is not an acceptable option now,
because I have already filled half of 10TB by data.
I'll be happy if 'xfs_growfs -l" option is implemented.

Anyway, thank you for your advice.

With some careful, very-much-unsupported use of xfs_db, you could shrink the log while offline. It's not supported, and I'd feel a bit frightened of doing this with a large important filesystem.

But essentially you -could- follow this procedure:

Unmount the filesystem so that the log is clean.
run xfs_repair -L to zero out the log.
run xfs_db to change "logblocks" in each superblock to a smaller value
 - do NOT change the "logstart" or any other superblock values
cross your fingers & remount

I haven't tested this locally, at least not recently. You didn't hear this from me, and if it breaks, you get to keep both pieces... at a minimum you might wait for David or Nathan to chime in and sanity-check my suggestion. And even if they say it seems reasonable, I'd suggest testing on an unimportant filesystem a few times to be sure.

-Eric


<Prev in Thread] Current Thread [Next in Thread>