Actually, I'm pretty sure you _never_ need to exportvg in order to have
it work on another system. That's one of the great things about AIX LVM,
because it means you can move a VG to another system after a hardware
problem, and not have any problems importing it (journaled fs also helps).
On Tue, 13 Mar 2001, Alexander Viro wrote:
On Mon, 12 Mar 2001, Daniel Phillips wrote:
I'm not at all comfortable with the way we are handling i_size right
now - it gets set in a funny way:
- vmtruncate sets i_size lower
- _commit_write sets it higher
Coding for this feels
" " == Daniel Phillips [EMAIL PROTECTED] writes:
Only file_write, truncate and high level filesystem code code
should set i_size.
That's only true for local filesystems. Networked filesystems can
decide to set i_size at any time, since the server is the ultimate
authority on a
On Thu, 15 Mar 2001, Trond Myklebust wrote:
" " == Daniel Phillips [EMAIL PROTECTED] writes:
Only file_write, truncate and high level filesystem code code
should set i_size.
That's only true for local filesystems. Networked filesystems can
decide to set i_size at any time,
" " == Daniel Phillips [EMAIL PROTECTED] writes:
On Thu, 15 Mar 2001, Trond Myklebust wrote:
" " == Daniel Phillips [EMAIL PROTECTED] writes:
Only file_write, truncate and high level filesystem code code
should set i_size.
That's only true for local
