Diane -
Here's a short LIST.READU envelope that replaces dev/inode with filenames.
Look up these UV-supplied tools that tie device Inode to the filename:
ACCOUNT.FILE.STATS
LIST.FILE.STATS
STAT.FILE
UNIVERSE.STAT.FILE
It relies on regularly running ACCOUNT.FILE.STATS to keep
Better yet, write an i-descriptor-friendly function to extract STATUS
FILEINFO info, then use it in DICT VOC I-descripters to use with SELECT
LIST directly.
On 3/16/2012 5:00 PM, LeRoy Dreyfuss wrote:
A program that uses either the FILEINFO() function or the STATUS statement will
produce
Thanks!!!
Quoting Charles Stevenson stevenson.c...@gmail.com:
Diane -
Here's a short LIST.READU envelope that replaces dev/inode with filenames.
Look up these UV-supplied tools that tie device Inode to the filename:
ACCOUNT.FILE.STATS
LIST.FILE.STATS
STAT.FILE
You can also use UniAdmin.
That will show the file name as well.
On 17/03/2012 17:12, dia...@aptron.com wrote:
Thanks!!!
Quoting Charles Stevensonstevenson.c...@gmail.com:
Diane -
Here's a short LIST.READU envelope that replaces dev/inode with filenames.
Look up these UV-supplied tools
Anyone have an easy way to do this?
In the past I've run a batch routine to just query each and every Universe file
for it's inode and device and build a table of these
Every week
Seems like a great amount of overkill to me.
You could also mod the CREATE-FILE command to sniff it and make an
Hi,
There is no trivial way to do this because a single inode may correspond to
multiple file names if there are links.
A useful trick if you run ACCOUNT.FILE.STATS from time to time is to look at
the data file that it generates. This includes the
inode numbers.
Of course, a better solution
What about doing a df, then loop through each filesystem that is a universe
directory, and run ls -i (looping through each directory)
Then index the resulting ls's ?
George
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On
Or loop through df with 'cd filesystemname ; find . -ls -depth | awk {print
$x $y}' where $x and $y are the
Column numbers for the inode number and the filename
Of course, this would be for unix only
George
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[george@alpha]$ find . -depth -ls | awk '{print $1,$11}' | pg
16390568 ./IP.KEYS.HOLD/OVER.30
16390570 ./IP.KEYS.HOLD/.Type30
16390569 ./IP.KEYS.HOLD/DATA.30
16390567 ./IP.KEYS.HOLD
15795741 ./VME-ADV-FILE/OVER.30
15795743 ./VME-ADV-FILE/.Type30
15795742 ./VME-ADV-FILE/DATA.30
15795740
Try ls -li |grep inode# in the directory where the file is likley to be or
ls -liR / |grep inode# to look everythere.
You may need root permissions to check some files.
NO warranty!
Don Robinson
From: Wjhonson wjhon...@aol.com
To: u2-users@listserver.u2ug.org
Sent: Friday, March 16, 2012
Are inodes unique across all devices? I was under the impression that they
were not, and therefore you need both for a unique correspondence
-Original Message-
From: Don Robinson donr_w...@yahoo.com
To: U2 Users List u2-users@listserver.u2ug.org
Sent: Fri, Mar 16, 2012 12:58 pm
As far as I understood, no, they are unique only to their device, so you could
have multiple files
With the same inode in different filesystems.
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson
Sent:
It seems like an on the fly scan across all possible filesystems would be
really slow.
I can't see how you can escape having a cross reference that gets rebuilt
periodically.
No one is going to want to wait a minute in interactive mode for a response.
No one else has encountered the issue that
I did a couple tests using:
find (device) -xdev -inode # -print
And it wasn't too much of a delay (instant to few seconds)
George
Other than that I just ran the following (for xref method)
cd /data2 ; find . -depth -ls | awk '{print $1,$11}' /tmp/inodelist and it
ran fairly fast, so if
Just thinking, you could also add a modification time to the find, (if your
doing xrefs), and only
Reindex those files that have been changed (or created) since the last time you
ran it? If you
Use the device and inode as key in your xref, it will overwrite any deleted
files where the inode
Is
A program that uses either the FILEINFO() function or the STATUS statement will
produce what you need, and should work cross-platform. Select against the VOC
and filter out what you don't need, i.e. remote files, Q-pointers etc.
Regards,
LeRoy
Sent from my iPhone 4
On Mar 16, 2012, at 3:23
I have a utility named FLIST.READU that replaces the inode from the
standard LIST.READU output with the file name. It uses ls -i, so it's
limited to files in the account you run the command from, though. Works
fine for us because all of our users work out of the same account. This
is the
The file could be in any account, so you'd have to expand this to select every
file in every account
-Original Message-
From: LeRoy Dreyfuss lfd...@gmail.com
To: U2 Users List u2-users@listserver.u2ug.org
Sent: Fri, Mar 16, 2012 3:00 pm
Subject: Re: [U2] Turn a device and inode into
This only works if you have a single device, since the inode is not unique
cross-device, only unique on a device
-Original Message-
From: John Hester jhes...@momtex.com
To: U2 Users List u2-users@listserver.u2ug.org
Sent: Fri, Mar 16, 2012 3:25 pm
Subject: Re: [U2] Turn a device and
We use the following subroutine. Pass in the filename in variable FNAME. In
the mainline is 'THIS.ACCOUNT' and of course the F.FILESTATS.XREF file variable.
We then use this information in our expanded record locks display so that we
can show real file names.
UPDATE.XREF: *;*
*
CRT
I swear I wrote a new version of LIST.READU at one time where I dealt with this
and listed the file where the item was locked, but I can't find it anywhere.
And now, of course, I'm obsessed with finding it. If I find it I'll post it.
-Dianne
Quoting Wjhonson wjhon...@aol.com:
It seems like
In my case, you do not know the filename.
The only thing you know is the Inode and Device.
The task is to *find* the filename based on knowing only the Inode and Device
-Original Message-
From: Buss, Troy (Logitek Systems) (Logitek Systems)
troy.b...@nordsonasymtek.com
To: U2 Users
It works fine if you have multiple devices because you can only run it
against one account and one device at a time. ls -i doesn't span
directory hierarchies or devices. You do at least have to know what
device the file in question is on, but if you don't know that there's no
tool that will
The provided code does not specify a device, so how can you select a device
even if you know it?
It doesn't seem to be changing devices
-Original Message-
From: John Hester jhes...@momtex.com
To: U2 Users List u2-users@listserver.u2ug.org
Sent: Fri, Mar 16, 2012 4:41 pm
Subject:
If you execute ls -i from within UV, it's going to list the files in
the directory where the account you're sitting in resides. My code
example isn't written to be able to switch devices because that's of no
use to me in the context of listing locked production files in our
environment. If you
The lock table spans all accounts.
To list the file associated with any particular lock, you have to span all
devices, not just a device.
You can't assume that you know the account in which a locked inode resides.
-Original Message-
From: John Hester jhes...@momtex.com
To: U2 Users
*I* can assume because in our environment there is one production
account on one device. I wasn't suggesting that this specific utility
would be of any use in any other environments, only that the underlying
OS-level command could be used in a similar way to translate an inode
into a file name.
Only if you run it on the device to which that inode refers.
If you run it on another device, you won't get a valid response.
In order to know how to get *to* the device in question, you have to already
know to what account it refers.
That's circular.
The point is, in the List Locks you do not
28 matches
Mail list logo
