FileSystem Full - when It is NOT FULL

From: Joe Spanicek <joe_at_resptk.bhp.com.au>
Date: Wed, 4 Dec 1996 11:08:06 +1100

Hi All,

I just recently started getting file system full messages
when the actual file system is not full.

We are running DU3.0b on a DEC3000/300. UNAME is:

        OSF1 qmp2 V3.0 358.78 alpha

The result of the 'df -k' command is:

qmp2{root}25: df -k
Filesystem 1024-blocks Used Avail Capacity Mounted on
/dev/rz0a 63231 32282 24625 57% /
/proc 0 0 0 100% /proc
/dev/rz0g 770036 616377 76655 89% /usr
/dev/rz6a 1618686 1456829 0 100% /home
/dev/rz2c 159702 159702 0 100% /cdrom

The result of 'du -k /home' command is:

.
.
.
475 /home/transfer/zal
216 /home/transfer/dcl
1877 /home/transfer/cgl
1321 /home/transfer/bin
95 /home/transfer/src
3985 /home/transfer
90827 /home

I searched through the '/home/ directory and could not
find any huge file been generated. So I believe the
kernal is having problems or has a bug.

The disk this occurs on is given by:

qmp2{root}6: scu -f /dev/rrz6c
scu> show device
Inquiry Information:

                      SCSI Bus ID: 0
                   SCSI Target ID: 6
                  SCSI Target LUN: 0
           Peripheral Device Type: Direct Access
             Peripheral Qualifier: Peripheral Device Connected
            Device Type Qualifier: 0
                  Removable Media: No
                     ANSI Version: SCSI-2 Compliant
                     ECMA Version: 0
                      ISO Version: 0
             Response Data Format: ANSI SCSI-2
            Terminate I/O Process: 0
        Asynchronous Notification: 0
                Additional Length: 31
               Soft Reset Support: 0
          Command Queuing Support: 1
           Linked Command Support: 1
       Synchronous Data Transfers: 1
     Support for 16 Bit Transfers: 0
     Support for 32 Bit Transfers: 0
      Relative Addressing Support: 0
            Vendor Identification: DEC
           Product Identification: RZ29B (C) DEC
          Firmware Revision Level: 0014


This disk has recently been installed on the system and
a new kernal compiled. The problem only started occuring
when a user started running a particular script which
generates files for a plotting application which resides
in the '/home' partition. In all, this does not by any
means generate 1gig of temp data.

Has anybody else seen this problem and know of a fix ??

Regards Joe Spanicek
Received on Wed Dec 04 1996 - 01:23:35 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:47 NZDT