Memory issues while gathering TAC-PAC?

Unanswered Question
Jun 3rd, 2009

When I contact TAC, they continually ask for a sh tech as the first step of the process. This generates 100MB+ files, which aren't terribly handy to email.

I issued a tac-pac slot0:/filename command, and the process errored out after a few minutes:

gunzip: /volatile/show_tech_lc_out_10.gz: unexpected end of file

gunzip: /volatile/show_tech_lc_out_9.gz: unexpected end of file

grep: write error: No space left on device

cat: write error: No space left on device

cat: write error: No space left on device

cat: write error: No space left on device

cat: write error: No space left on device

I verified that I had 2GB free on disk0, and issued the command again- now I get the following immediately:

date: write error: No space left on device

There were some files with appropriate names in the volatile:// directory, all with 0 byte sizes. I deleted them, but still have no room left in volatile:

# dir volatile:

Usage for volatile://sup-local

209715200 bytes used

0 bytes free

209715200 bytes total

Logs show:

2009 Jun 3 08:50:38.152 [13314]: CLIC-3-FAILED_UNLINK_FILE: Couldn't unlink file /rd/fifo/cli-fifo-13314-0

Just wondering if anybody's seen this behavior before, and if there was a fix?

TAC support hasn't fully firmed up for the NXOS devices, I'm discovering.

I have this problem too.
1 vote
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.

Actions

This Discussion