Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Linux\s+Sparse\s+Files\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Linux\s+Sparse\s+Files\s*$/: 2 ]

Total 2 documents matching your query.

1. Linux Sparse Files (score: 1): Author: "Robinson, Brian D." <brian.robinson AT NSCORP DOT COM>; Date: Tue, 3 Oct 2006 10:03:30 -0400; We are running AIX 5.2.0, TSM 5.2.6 server, with a TSM Client 5.3.4 running on Red Hat version 4. We seem to be having an issue with Linux sparse files - see description below. The manual says that T; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2006-10/msg00005.html (11,901 bytes)
2. Re: Linux Sparse Files (score: 1): Author: Richard Sims <rbs AT BU DOT EDU>; Date: Tue, 3 Oct 2006 10:42:19 -0400; Brian - You'll have to examine the scheduler log and possibly the dsmerror.log to determine why the backup was "unsuccessful". My cumulative notes on sparse file handling in ADSM QuickFacts may be he; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2006-10/msg00008.html (11,120 bytes)

Current List: 1 - 2
Page: [1]