Peter Braam wrote:
CFS recently posted a C program that can scan the disks (even while Lustre is mounted) and generate pathname lists. Our main purpose was backups. This program should be usable for other purposes.yes, this program is named e2scan, which is a program using libext2fs to find inodes with ctime or mtime newer than a given time and print out their pathname. this program can be found in bug10929, i also attached it here.Huangwei, could you point out how this works?
Simple usage example for e2scan: e2scan -u -f filename devthis will create a file named modified_pathnames include all modified file's pathname.
more detail of e2scan can be found in their man page.
- peter - Felix, Evan J wrote:The problem becomes that it is very time consuming to run stat on every file of the MDS. We have used a multi-threaded python program to walk the entire filesystem fairly effectively on our two large Lustre systems. I released one of them a while back to the mailing list, and it should be in the archives somewhere. If you cant locate it send me a mail, and I'll send it on to you. The released version was designed to expire files when they have been on the file system for a long time, but it doesn't have to, as it also collects usage data for files, and directories. I've heard rumors that someone in CFS is working on and MDS scanning utility that should be more efficient, but until we see it I have no idea how well it works.. Evan-----Original Message-----From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kaizaad BilimoryaSent: Thursday, January 11, 2007 7:31 AM To: [email protected] Subject: [Lustre-discuss] file stat in lustre Hello,We would like to build an informational page that will provide users with stats (size, name, path, mod time,...) on files they have in the lustre filesystem (and maybe store it in a db). I can use "lfs" to get strip and OST info but not "stat" info. We could build some perl tools (probably already out there) which would traverse the filesystem and give us this information, but I would like to know if there is a better or efficient way to do this.Or maybe there is already a lustre utility that can give me the stat info on a file just by querying the MDS server instead of traversing the entire lustre filesystem? Or maybe this is not a good approach? Something better?thanks -k _______________________________________________ Lustre-discuss mailing list [email protected] https://mail.clusterfs.com/mailman/listinfo/lustre-discuss_______________________________________________ Lustre-discuss mailing list [email protected] https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
e2scan.tar.gz
Description: GNU Zip compressed data
_______________________________________________ Lustre-discuss mailing list [email protected] https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
