On Tue, Nov 13, 2007 at 11:57:41AM -0700, Scott Kaiser wrote: > Two options: > > 1. use a command from the database edition that provides this sort of > mapping: > vxstorage_stats > Although this command was targeted at the database market, it works on > any file. > The requirements and such are in chapter ~8 of the DBED Administrator's > Guide. Man page below. Note that, at least in the past, the developers > stuck this and other commands in their own directory, rather than > provide links into /opt/VRTS/bin, so you may have to edit your PATH > variable. > > 2. use fsdb to get the block map of the file; use that to calculate the > offsets yourself and figure out the corresponding volume locations; use > those to figure out the subdisk locations. > > Note that a file can have >1 extent, and an extent can span subdisks, so > a file can very possibly reside on multiple LUNs.
Thank you Scott for the tips. Unfortunately we don't use DBE so the only way to do that is the second one. Regards przemol ---------------------------------------------------------------------- "Kup bilet na najlepsze zawody Freestyle Motocross - DIVERSE Night of the Jupms!" http://link.interia.pl/f1c5f _______________________________________________ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
