Re: disregard mod/access time

From: Jason de la Fuente (delalist_at_HOTMAIL.COM)
Date: 04/27/05

  • Next message: Cahyadi, Edi: "Re: Change Inode and modification time" 
    Date:         Tue, 26 Apr 2005 23:17:19 -0500
To: aix-l@Princeton.EDU

    I found the command 'fsdb' which does show an example that appears to be
    changing the inode number for a directory. I haven't had a chance to play
    with it and I wasn't sure if there was a "simple" way of accomplishing the
    same thing.

    Has anyone on the list used fsdb before?

    >From: Justin Bleistein <justin.bleistein@TOWERSPERRIN.COM>
    >Reply-To: IBM AIX Discussion List <aix-l@Princeton.EDU>
    >To: aix-l@Princeton.EDU
    >Subject: Re: disregard mod/access time
    >Date: Tue, 26 Apr 2005 16:52:38 -0400
    >
    >I doubt if you're going to be able to change the inode. Especially, on non
    >open sourced Unix systems.
    >That's a kernel thing.
    >Thanks.
    >
    >--Justin Richard Bleistein
    > AIX Systems Administrator
    >
    >
    >
    >
    >
    >
    >
    >Jason de la Fuente <delalist@HOTMAIL.COM>
    >Sent by: IBM AIX Discussion List <aix-l@Princeton.EDU>
    >04/26/2005 04:34 PM
    >Please respond to
    >IBM AIX Discussion List <aix-l@Princeton.EDU>
    >
    >
    >To
    >aix-l@Princeton.EDU
    >cc
    >
    >Subject
    >disregard mod/access time
    >
    >
    >
    >
    >
    >
    >found it, touch -ma.
    >
    >Still trying to find a way to change the inode # though.
    >
    >_________________________________________________________________
    >FREE pop-up blocking with the new MSN Toolbar – get it now!
    >http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
    >
    >
    >
    >
    >
    >
    >NOTICE: This communication may contain confidential, proprietary or
    >legally privileged information. It is intended only for the person(s) to
    >whom it is addressed. If you are not an intended recipient, you may not
    >use, read, retransmit, disseminate or take any action in reliance upon it.
    >Please notify the sender that you have received it in error and
    >immediately delete the entire communication, including any attachments.
    >Towers Perrin does not encrypt and cannot ensure the confidentiality or
    >integrity of external e-mail communications and, therefore, cannot be
    >responsible for any unauthorized access, disclosure, use or tampering that
    >may occur during transmission. This communication is not intended to
    >create or modify any obligation, contract or warranty of Towers Perrin,
    >unless the firm clearly expresses such an intent.
    >

    _________________________________________________________________
    Don’t just search. Find. Check out the new MSN Search!
    http://search.msn.click-url.com/go/onm00200636ave/direct/01/

  • Next message: Cahyadi, Edi: "Re: Change Inode and modification time"

    Relevant Pages

    • Re: Root FS corruption
      ... Of course, it wasn't the fault of nextboot itself, ... I experienced the exact same corruption some months ago with a RELENG_6 ... involving ls -i and fsdb. ... current inode: directory ...
      (freebsd-current)
    • Recovering a deleted open file with fsdb.
      ... What made this specifically aggravating was that it was "so close". ... But, fsdb simply wouldn't work. ... I was able to located the inode, ... Every article I could find on "recovering deleted files" were all based on ...
      (comp.unix.solaris)
    • Re: disregard mod/access time
      ... I doubt if you're going to be able to change the inode. ... open sourced Unix systems. ... AIX Systems Administrator ... immediately delete the entire communication, ...
      (AIX-L)
    • Re: How to delete a directory...
      ... The problem is that the reference count for the directory is 3, ... than the normal 2 for an empty directory. ... More likely, though, is that a crash or bug corrupted the inode entry. ... use fsdb to change the reference count in inode 570 from ...
      (comp.unix.aix)
    • Re: Recovering a deleted open file with fsdb.
      ... > What happened was a DB file was rm'd, but the database was still running, ... Not the inode of that dir itself, ... > But, fsdb simply wouldn't work. ... and was able to recover the inconsistent file from ...
      (comp.unix.solaris)