xfs
[Top] [All Lists]

Re: xfs setting inode ctime

To: Dean Roehrich <roehrich@xxxxxxx>
Subject: Re: xfs setting inode ctime
From: vijaya saradhi uppaluri <uvsaradhi@xxxxxxxxx>
Date: Fri, 1 Oct 2004 09:47:03 +0530
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <200409291514.i8TFE3xM456020@tulip-e236.americas.sgi.com>
References: <200409291514.i8TFE3xM456020@tulip-e236.americas.sgi.com>
Reply-to: vijaya saradhi uppaluri <uvsaradhi@xxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
Dean,

 Thanks for your response. I am currently working on stack of file
systems where I set the attribute ATTR_CTIME and expect the underlying
file-system to set the ctime to the value I pass. It is working on
other file-systems(ext2) on linux.

-Thanks,
 Saradhi.


On Wed, 29 Sep 2004 10:14:03 -0500, Dean Roehrich <roehrich@xxxxxxx> wrote:
> >From:  vijaya saradhi uppaluri <uvsaradhi@xxxxxxxxx>
> 
> >Is there any logical reason behind this? Why does XFS_AT_CTIME is
> >coupled with ATTR_DMI?
> >
> >Is there any goodway of setting ctime attribute of xfs?
> >
> >I observed that other file-systems sets the ctime accordinlgy if
> >ATTR_CTIME flag is set.
> 
> XFS inherits this restriction from Irix, where userspace is not allowed to set
> ctime.  The Irix utime(2) and utimes(2) system calls allow only atime and
> mtime to be set, and always set ctime to the current time.  I see the same in
> Solaris 9 and RH9 manpages.
> 
> How are you changing ctime?
> 
> Dean
> 



-- 
-U. Vijaya Saradhi,
 Agami Systems,
 Ph.No: +91-9849513967.


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