I am having the same problem here. My /data/amanda directory cleary contains
data. I am running:
amflush -f DailySet1 and this is what I get
Today is: 20040204
Flushing dumps in 20031209, 20031210, 20031218, 20040103, 20040115, 20040121,
20040123, 20040124 to tape drive "/dev/nst0".
Expecting tape DMP13 or a new tape. (The last dumps were to tape DMP12)
Are you sure you want to do this [yN]? y
amflush: datestamp 20040204
driver: pid 22039 executable driver version 2.4.3
taper: pid 22040 executable taper version 2.4.3
taper: page size is 4096
taper: buffer size is 32768
taper: buffer[00] at 0x400db000
taper: buffer[01] at 0x400e3000
taper: buffer[02] at 0x400eb000
taper: buffer[03] at 0x400f3000
taper: buffer[04] at 0x400fb000
taper: buffer[05] at 0x40103000
taper: buffer[06] at 0x4010b000
taper: buffer[07] at 0x40113000
taper: buffer[08] at 0x4011b000
taper: buffer[09] at 0x40123000
taper: buffer[10] at 0x4012b000
taper: buffer[11] at 0x40133000
taper: buffer[12] at 0x4013b000
taper: buffer[13] at 0x40143000
taper: buffer[14] at 0x4014b000
taper: buffer[15] at 0x40153000
taper: buffer[16] at 0x4015b000
taper: buffer[17] at 0x40163000
taper: buffer[18] at 0x4016b000
taper: buffer[19] at 0x40173000
taper: buffer structures at 0x4017b000 for 240 bytes
driver: send-cmd time 0.018 to taper: START-TAPER 20040204
driver: adding holding disk 0 dir /data/amanda size 3145728
reserving 3145728 out of 3145728 for degraded-mode dumps
taper: read label `DMP13' date `20040108'
taper: wrote label `DMP13' date `20040204'
So, amflush writes the tapelable and than just stops. The tape is good
(tested), it does that with all 25 Tapes in my tapecycle. Nothing is written in
the /temp/amanda log directory. If I kill the amflush process I get an email
telling me that the dump didn't end correctly.
Axel
> On Wed, Feb 04, 2004 at 07:01:31PM +0530, Rohit wrote:
> > > Is there actually anything in the holdingdisk?
> > > Does amflush show you dumps to flush?
> >
> > -bash-2.05b$ /usr/sbin/amflush -f DailySet1
> > Scanning /backup...
> > lost+found: skipping cruft directory, perhaps you should delete
> it.> windows: skipping cruft directory, perhaps you should delete
> it.> 20040130: found Amanda directory.
> > 20040131: found Amanda directory.
> > 20031230: found Amanda directory.
> > 20040201: found Amanda directory.
> > 20040203: found Amanda directory.
> >
> > Multiple Amanda directories, please pick one by letter:
> > A. 20031230
> > B. 20040130
> > C. 20040131
> > D. 20040201
> > E. 20040203
> > Select directories to flush [A..E]: [ALL]
> >
>
> OK, please take that to the next logical step.
>
> Amanda is telling you you have "cruft directories" as well
> as "apparently good amanda directories". Is there anything
> in those directories? Perhaps your apparently good directories
> also contain "cruft", and only cruft *** .
>
> At the end of an amdump run amanda tries to remove the directory
> it was using. It "should" have already removed all files from
> those directories so a basic "rmdir" type remove should work.
> But if any "cruft" is left behind, the "rmdir" action will not
> remove the directory and it will "look like" there is still
> something needing flushing.
>
>
>
>
> ***
> cruft /kruhft/ [very common; back-formation from {crufty}]
> 1. n. An unpleasant substance.
> The dust that gathers under your bed is cruft;
> the TMRC Dictionary correctly noted that attacking it with
> a broom only produces more.
> 2. n. The results of shoddy construction.
> 3. vt. [from `hand cruft', pun on `hand craft'] To write
> assembler code
> for something normally (and better) done by a compiler (see
> {hand-hacking}).
> 4. n. Excess; superfluous junk; used esp. of redundant or
> superseded code.
> 5. [University of Wisconsin] n. Cruft is to hackers as gaggle is
> to geese;
> that is, at UW one properly says "a cruft of hackers".
>
> Source: Jargon File (4.3.0, 30 APR 2001)
>
> --
> Jon H. LaBadie jon AT jgcomp DOT com
> JG Computing
> 4455 Province Line Road (609) 252-0159
> Princeton, NJ 08540-4322 (609) 683-7220 (fax)
>
|
