Unable to create Large File System

[Praveen Bezawada]

Hi

when i issue the command
/usr/sbin/fsadm -F vxfs -o largefiles /praveen

where praveen is a mounted file system i'm getting the error
fsadm : set feature (LARGEFILES) failed,errno 25

What could be the problem.... please help...

[Andreas Voss]

Hi,

you have to use the device instead of the mount point. Ie:
fsadm -F vxfs -o largefiles /dev/vg01/lvol1

Regards

[Praveen Bezawada]

I have also tried that .... i got the error
vxfs fsadm /dev/vg02/lvol1 is not the root inode of a vxfs file system. Even though it is VXFS file system.

[Andreas Voss]

Hi,

have you installed OnlineJFS ?
If not you cannot use fsadm online. Then you have to umount the fs before doing fsadm.
When you do a search at the forum with keyword fsadm AND largefiles you can get many threads for this.

Regards

[John Palmer]

Hi,

You need to use the raw device filename eg /dev/vg02/rlvol1.

If you don't have ONLINEJFS and the filesystetem is mounted then you'll get the error 'fsadm /dev.... is currently mounted'

Unmount it, repeat the fsadm and it should work ok.

[Praveen Bezawada]

hi

I have OnLineJFS installed on the machine.and also have version 3 disk layout. Still the error

[John Palmer]

Well the error message indicates that this is a base JFS filesystem. What error message do you get if you specify the raw device 'dev/vg??/rlvol?'?

[federico_3]

Once installed JFS online, the command you have to type is:

fsadm -F vxfs -o largefiles /mount_point

in order to verify the File System characteristics type:

mkfs -m /dev/vgxx/lvx

It should be OK!

federico

[Praveen Bezawada]

Hi Palmer

The error i get when i use the ogical volume device name is

vxfs fsadm /dev/vg02/lvol1 is not the root inode of a vxfs file system.

Even though it is VXFS file system

[federico_3]

Also i get the same error if i try to convert the FS with the logical volume; but if i use the mount point it works fine!

If you have installed JFS online use:

/usr/sbin/fsadm -F vxfs -o largefiles /praveen


Federico

[John Palmer · Accepted solution]

What do you get if you do:-

fsadm -F vxfs -o largefiles /dev/vg02/rlvol1

note the 'rlvol1' not 'lvol1'

[Andreas Voss]

Hi,

here an extrat of a document:

Verify with the fsadm() command using the mountpoint:
fsadm -F vxfs /(mountpoint)

largefiles

If this returns with errno 25, then Advanced JFS is not installed. The unmounted device file must be used.

swlist -l fileset|grep -i journal

Check for:

JournalFS <---------- base JFS
AdvJournalFS <---------- Advanced JFS


Verify with the fsadm() command using the umounted raw device:
fsadm -F vxfs /dev/vg#/rlvol#

largefiles


Verify with a dd() command. This verifies that the file system is capable of creating a largefile. If it is not then an IO error will result.
dd if=/stand/vmunix of=/(mountpoint)/sparse bs=1024k seek=3000

This creates a 3 GB sparse file.



Make sure the current JFS patches are loaded on the system.

PHCO_14628 :LVM:commands:cumulative:
PHCO_14511 :libc:strcol:malloc:free:memccpy:PHCO_12923 :fsck_vxfs:VxFS:JFS:
PHCO_12140 :cleanup:patch backup:depot:ipd:
PHKL_10459 :SystemV semaphores:semop(2):cumulative:
PHKL_10461 :pfdat:page unlocking:PHKL_13951 :Power:Fail:I/O:SCSI:stape:
PHKL_13044 :SCSI:pass-thru:spt:spt0:NIKE:SAM:hang:
PHKL_12340 :VxFS:JFS:fsck(1M):cumulative:
PHKL_14686 :VM:LVM:I/O:JFS:mprotect:SCSI:PM:cumulative:
PHKL_13573 :VxFS:JFS:corruption:hang:cumulative:
PHKL_14280 :hpux(1M):loader:large:kernels:
PHNE_13800 :mux:pty:mux2:zmuxdiag:J2096A:VTIME:
PHNE_14498 :HP-PB:FDDI:cumulative:PHNE_6190 :DDFA:ocd:
PHCO_13251 :SAM:cumulative:PHNE_7671 :ARPA:telnet:
PHKL_8780 :GSC:HSC:MP:autochanger:semaphore:PHNE_13416 :100BT:HP-PB:T600:
PHCO_12435 :fsck_hfs(1M):cumulative:PHCO_10578 :extendfs_hfs:fragments:40GB:
PHNE_14271 :XPORT:ARPA:Transport:

Also put another doc at attachment.

Regards

[James R. Ferguson]

Praveen:

From document #A5005662: The error occurs because you are trying to perform the fsadm
command on a mounted filesystem, but you do not have the On-line JFS product. If you do not have OnlineJFS, you can enable the
largefiles feature by first unmounting the filesystem and then running fsadm on the device name rather than the mount point:

# umount /vxfs
# fsadm -F vxfs -o largefiles /dev/vg01/rlvol1

Some very good step-by-step information for enabling largefiles can be found in document #KBAN00000105. One item it notes is to insure that 'ulimit' is unlimited.

...JRF...

[Praveen Bezawada]

HI

I have AdvJournalFS installed on the machine. now i have succeed in enabling large file systems using
fsadm -F vxfs -o largefiles /dev/vg02/rlvol1

(using the raw device file ) Note here i have not unmounted the file system but still i could do it when i use raw device file but when i try to use the name of the mounted directory it gives the error 25...

[Praveen Bezawada]

Hi

I cannot enable large files without umounting as i said by mistake in my last reply....

Regards

[Praveen Bezawada]

Hi

Though my problem as such as been solved, I have one more question.

when I do
swlist -l product | grep -i journal

AdvJournalFS the advanced VXFS file system
JournalFS the base VXFS filesystem

are shown. But still when i try to enable large files on a mounted file system i get error 25 , implying i have not installed Advanced OnlineJFS
But could be problem......

Regards

[Stefan Farrelly]

On a system with OnlineJFS installed my swlist -l product | grep -i journal gives the same results as you.

However, do a swlist -l bundle | grep -i jfs and this will confirm OnlineJFS is installed if it returns;

B3929BA B.11.00 HP OnLineJFS (Advanced VxFS)

[Stefan Farrelly]

On a system with OnlineJFS installed my swlist -l product | grep -i journal gives the same results as you.

However, do a swlist -l bundle | grep -i jfs and this will confirm OnlineJFS is installed if it returns;

B3929BA B.11.00 HP OnLineJFS (Advanced VxFS)

I think there are still conditions where you cant set largefiles on a mounted filesystem, ive had this problem myself. If the filesystem is too full or heavily in use it wont take it, Ive had to unmount it myself to set it.

[John Palmer]

One other possibility concerns how you may have applied patches.

Have a look at the attached document which explains how to apply patches if you have Advanced JFS installed.