cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1125
Views
0
Helpful
4
Replies

WAAS - Disk Space Error

b.petronio
Level 3
Level 3

Hi all,

Is this Syslog Error Message affecting statistics in % Compression?

What is the cause of this ? It is tunned, or should be automaticaly resolved?

Best Regards,

Bruno Petrónio

*** Output ***

2009 Jul 30 11:33:13 wae so_dre: %WAAS-RE-3-690464: (74488:2) RE File Manager error: filemgr_state::do_io (segments) call pwrite(90, 0x51e7e008, 65536, 68485120): No space left on device

2009 Jul 30 11:33:13 wae so_dre: %WAAS-RE-3-690432: (74673:2) FileMgr failed in writing data-segment start at id=834779, error=0xfffffc09--Disk is full

2009 Jul 30 11:33:13 wae so_dre: %WAAS-RE-3-690464: (112823:2) RE File Manager error: filemgr_state::do_io (segments) call pwrite(90, 0x5140e008, 65536, 69271552): No space left on device

2009 Jul 30 11:33:13 wae so_dre: %WAAS-RE-3-690432: (112995:2) FileMgr failed in writing data-segment start at id=834791, error=0xfffffc09--Disk is full

wae#show disks details

Physical disk information:

disk00: Present WD-WCANY3489733 (h02 c00 i00 l00 - Int DAS-SATA)

238472MB(232.9GB)

disk01: Present WD-WCANY3489714 (h02 c00 i01 l00 - Int DAS-SATA)

238472MB(232.9GB)

Mounted file systems:

MOUNT POINT TYPE DEVICE SIZE INUSE FREE USE%

/sw internal /dev/md0 991MB 912MB 79MB 92%

/swstore internal /dev/md1 991MB 459MB 532MB 46%

/state internal /dev/md2 5951MB 191MB 5760MB 3%

/local/local1 SYSFS /dev/md4 11903MB 601MB 11302MB 5%

.../local1/spool PRINTSPOOL /dev/data1/spool 991MB 32MB 959MB 3%

/obj1 CONTENT /dev/data1/obj 125975MB 1013MB 124962MB 0%

/dre1 CONTENT /dev/data1/dre 59515MB 59514MB 1MB 99%

/ackq1 internal /dev/data1/ackq 1189MB 32MB 1157MB 2%

/plz1 internal /dev/data1/plz 2379MB 65MB 2314MB 2%

Software RAID devices:

DEVICE NAME TYPE STATUS PHYSICAL DEVICES AND STATUS

/dev/md0 RAID-1 NORMAL OPERATION disk00/00[GOOD] disk01/00[GOOD]

/dev/md1 RAID-1 NORMAL OPERATION disk00/01[GOOD] disk01/01[GOOD]

/dev/md2 RAID-1 NORMAL OPERATION disk00/02[GOOD] disk01/02[GOOD]

/dev/md3 RAID-1 NORMAL OPERATION disk00/03[GOOD] disk01/03[GOOD]

/dev/md4 RAID-1 NORMAL OPERATION disk00/04[GOOD] disk01/04[GOOD]

/dev/md5 RAID-1 NORMAL OPERATION disk00/05[GOOD] disk01/05[GOOD]

Disk encryption feature is disabled.

wae# sho disks failed-disk-id

Disk location Serial Number

wae# sho disks failed-sectors

disk00

=========

(none)

disk01

=========

(none)

wae#

1 Accepted Solution

Accepted Solutions

Bruno,

I suspect you are running into bug CSCsy47235. When the amount of memory in the WAE changes, the disk allocations change as well. The release notes for the defect state what additional steps needs to be taken after the change in memory.

If you have any additional questions, please let me know.

Regards,

Zach

View solution in original post

4 Replies 4

Zach Seils
Level 7
Level 7

Bruno,

How long have you been seeing this message? Have you recently upgraded the software version of amount of memory in the WAE?

Regards,

Zach

Zach, i have 5 syslog files full of this message.

I recently upgrade the memory of the appliance from 1GB to 2GB. (WAE-512)

The software version was not upgraded lately. (4.1.3a)

Any ideas ?

Best Regards,

Bruno Petrónio

Bruno,

I suspect you are running into bug CSCsy47235. When the amount of memory in the WAE changes, the disk allocations change as well. The release notes for the defect state what additional steps needs to be taken after the change in memory.

If you have any additional questions, please let me know.

Regards,

Zach

Thank You very much Zach,

It seems to be the case.

It was a Demo in a client, which in some time we decide to upgrade the memory, cause a persistent tfo limition alarm.

The final results were not good about % of Optimization and Compression/Traffic Reduction.

But, what the hell, we are always learning !

Thanks a lot.

Bruno Petrónio