Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*short\s+write\s+\-\s+could\s+that\s+mean\s+that\s+the\s+\"use\"\s+on\s+holdingdisk\s+is\s+too\s+small\?\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*short\s+write\s+\-\s+could\s+that\s+mean\s+that\s+the\s+\"use\"\s+on\s+holdingdisk\s+is\s+too\s+small\?\s*$/: 3 ]

Total 3 documents matching your query.

1. Re: short write - could that mean that the "use" on holdingdisk is too small? (score: 1): Author: Jon LaBadie <jon AT jgcomp DOT com>; Date: Fri, 31 Dec 2004 11:09:30 -0500; A grep for "short write" in the source files shows it present in only two files, taper.c and tapeio.c. This confirms my notion on reading your note that it is a tape problem, not a holding disk probl; /usr/local/webapp/mharc-adsm.org/html/Amanda-Users/2005-01/msg00002.html (12,809 bytes)
2. Re: short write - could that mean that the "use" on holdingdisk is too small? (score: 1): Author: Peter Guhl <pgnews AT siconline DOT ch>; Date: Thu, 13 Jan 2005 17:12:37 +0100; Therefore it was pure luck when it did fit? The strange thing is that amflush on the next tape (manually) is causing "short write" too even though the stuff left at the holding disk is only 5% of the; /usr/local/webapp/mharc-adsm.org/html/Amanda-Users/2005-01/msg00160.html (12,501 bytes)
3. short write - could that mean that the "use" on holdingdisk is too small? (score: 1): Author: Peter Guhl <pgnews AT siconline DOT ch>; Date: Fri, 31 Dec 2004 15:02:15 +0100; Hello all This error happens all the time - but sometimes it vanishes and then it comes again. Now I have got the idea that the space allocated at the holding disk is too small (not the holding disk; /usr/local/webapp/mharc-adsm.org/html/Amanda-Users/2004-12/msg00177.html (10,561 bytes)

Current List: 1 - 3
Page: [1]