https://community.hpe.com/t5/operating-system-hp-ux/128-gb-filesystem-problems/m-p/2495668#M654886 No actually I haven't used such option to mount the filesystem. It is an explanation of the first part of the problem but now the second part is to be able to check the filesystem and mount it again and possibly without loosing data, any idea?<BR /><BR />Thanks, Enrico.<BR /> Tue, 20 Feb 2001 10:45:36 GMT Enrico Mazzoni 2001-02-20T10:45:36Z https://community.hpe.com/t5/operating-system-hp-ux/128-gb-filesystem-problems/m-p/2495666#M654884 Hi<BR /><BR /> I have an HP D270 (HP-UX 10.20) with a SCSI RAID system attached with 360GB available. I have create one volume group for the all RAID system<BR />and then two logical volumes of 128GB each with vxfs filesystem. One week ago I start to get problem with one of the filesystem, creating new files I got a message indicating that no space was left on device even if with "df" a can see that only 14% of the disk was used, so I "umount" the filesystem and check it with:<BR /><BR /> fsck -F vxfs -y -o full /dev/vg03/lvol1<BR /><BR />here you are the messages that I got:<BR /><BR />inode 967 dup block - extent start 58884096 offset 1 continue? (ynq)y<BR />.........<BR />.........<BR />.........<BR />inode 967 dup block - extent start 58884096 offset 19995 continue? (ynq)y<BR />inode 967 dup block - extent start 58884096 offset 19996 continue? (ynq)y<BR />inode 967 dup block - extent start 58884096 offset 19997 continue? (ynq)y<BR />inode 967 dup block - extent start 58884096 offset 19998 continue? (ynq)y<BR />inode 967 dup block - extent start 58884096 offset 19999 continue? (ynq)y<BR />inode 967 dup block - extent start 58884096 offset 20000 continue? (ynq)y<BR />vxfs fsck: dup block list overflow on inode 967# <BR /><BR /><BR /> Have you any idea and/or suggestion about such a problem? Patches to be installed or any other suggestion....<BR /><BR />Thanks, Enrico Mazzoni.<BR /><BR />------------------------------------------------<BR /><BR />Enrico MAZZONI<BR />INFN - Sezione di Pisa<BR />Via Livornese, 1291 I-56010 S.Piero a Grado (Pisa)<BR />Italy<BR /><BR />mailto:enrico.mazzoni@pi.infn.it<BR />Phone : +39-050-880297 / 282 / 313<BR />Phone @ CERN : +41-22-7671973<BR />Fax : +39-050-880317 Mon, 19 Feb 2001 15:31:53 GMT https://community.hpe.com/t5/operating-system-hp-ux/128-gb-filesystem-problems/m-p/2495666#M654884 Enrico Mazzoni 2001-02-19T15:31:53Z https://community.hpe.com/t5/operating-system-hp-ux/128-gb-filesystem-problems/m-p/2495667#M654885 Are your vxfs file systems mounted with "largefiles". If no, then this could be the problem. Mon, 19 Feb 2001 18:35:01 GMT https://community.hpe.com/t5/operating-system-hp-ux/128-gb-filesystem-problems/m-p/2495667#M654885 Byron Myers 2001-02-19T18:35:01Z https://community.hpe.com/t5/operating-system-hp-ux/128-gb-filesystem-problems/m-p/2495668#M654886 No actually I haven't used such option to mount the filesystem. It is an explanation of the first part of the problem but now the second part is to be able to check the filesystem and mount it again and possibly without loosing data, any idea?<BR /><BR />Thanks, Enrico.<BR /> Tue, 20 Feb 2001 10:45:36 GMT https://community.hpe.com/t5/operating-system-hp-ux/128-gb-filesystem-problems/m-p/2495668#M654886 Enrico Mazzoni 2001-02-20T10:45:36Z