Run an "ls" on the directory where the images are. You should see
something like:

|Image Identifier|C#|F#|Backup Time|.img
Server_1234567890_C1_F1_1234567890.img
Server_1234567890_C1_F2_1234567890.img
Server_1234567890_C1_F3_1234567890.img
Server_1234567890_C1_F4_1234567890.img
Server_1234567890_C1_F5_1234567890.img
Server_1234567890_C1_F6_1234567890.img
Server_1234567890_C1_F7_1234567890.img

The C# is copy number (generally 1)
The F# is fragment number (#1 thru however big the image is.)

If you see that you have images missing fragment #1 or with gaps in the
numbers, then you probably have partial images (the known issue with 5.1
DSSUs).

Run bpimagelist -L -backupid <ImageIdentifier> to query the catalog. If
the catalog does not recognize these files on the DSSU, then they are
orphaned. You can safely delete them.

-Jonathan

-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Nate
Sanders
Sent: Thursday, July 01, 2010 1:22 PM
To: Ed Wilts
Cc: Sanders, Nate; veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Disk Staging Flush

This is also a two parter because I'm getting errors about DSSU being
full and jobs unable to write to it despite the fact a Flush just ran..
So maybe there are orphaned files in there. Not sure how to verify that
on DSSU.


On 07/01/2010 11:54 AM, Nate Sanders wrote:
> >From the UI on the left is Storage Units. In here we have
dssu1,2,3,4.
> Right clicking on these and going to Change, then clicking on Disk
> Staging Schedule you see "Schedule type", which is (*) Frequency and
is
> set to 4 hours.
>
> So every 4 hours it's supposed to be expiring and copying to tape, no?
> So I guess what it does is copy, not remove. But the difference is
that
> it sets the data to expired so the new data can overwrite it, yeah? Is
> there a way to see what data on the DSSU is currently
locked/not-expired?
>
>
> On 07/01/2010 11:42 AM, Ed Wilts wrote:
>   
>> On Thu, Jul 1, 2010 at 11:35 AM, Nate Sanders
<sandersn AT dmotorworks DOT com<mailto:sandersn AT dmotorworks DOT com>> wrote:
>> NBU Ver: 5.1MP6
>>
>> Why is it that even after a DSSU flush and no other running jobs, the
>> file system still shows up as %100 usage from a Linux server?
>>
>> Several reasons.  First, there were lots of bugs in the DSSU code
back in 5.1.  If you can, you really should upgrade.
>> Secondly, until another job requires the space, the existing images
on disk won't get deleted until they expire.
>>
>> If another job starts up, does the space get deleted?
>>
>> Have you checked for orphan images on disk?  i.e. images on disk that
aren't in the catalog?  That was a common bug and required a manual
cleanup.
>>
>> Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE
>> ewilts AT ewilts DOT org<mailto:ewilts AT ewilts DOT org>
>>
[http://www.images.wisestamp.com/linkedin.png]Linkedin<http://www.linked
in.com/in/ewilts>
>>
>>
>>
>>   
>>     
>   

-- 
Nate Sanders            Digital Motorworks
System Administrator      (512) 692 - 1038




This message and any attachments are intended only for the use of the
addressee and may contain information that is privileged and
confidential. If the reader of the message is not the intended recipient
or an authorized representative of the intended recipient, you are
hereby notified that any dissemination of this communication is strictly
prohibited. If you have received this communication in error, please
notify us immediately by e-mail and delete the message and any
attachments from your system.
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu