06-16-2006
As of HP-UX 11i, nolargefiles is the default. When a filesystem is created, with either mkfs or newfs, a "-o largefiles" can enable the largefile capability. Or "-o nolargefiles" can be used to explicit request a limited filesystem.
After a filesystem has been created, fsadm can be used with "-o largefiles" to convert it to a largefile filesystem. In some cases, you can switch back with a "fsadm -o nolargefiles".
If you care which you have, you can use the options largefiles or nolargefiles when you mount the filesystem. This will not convert a filesystem, but the mount will fail if the filesystem does not match the flag used on mount.
If a filesystem is mounted on, say, /mountpoint, and you wonder what size files it supports, anyone (even non-root users) can do "getconf FILESIZEBITS /mountpoint". This will return 32 for "nolargefiles" filesystems and a larger integer for "largefiles" filesystems. (I am getting 42...so do not expect 64.)
All of this defines what the filesystem can handle. If your program is a 32 bit program, it may not be able to process large files. (But with special techniques, 32 bit programs can process largefiles.)
8 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi! I have a large set of pairs of text files (each pair in their own subdirectory) and each pair shares head/tail (a couple of first and last lines) but differs in the middle part. I need to delete the heads/tails and keep only the middle portions in which they differ. The lengths of heads/tails... (1 Reply)
Discussion started by: dobryden
1 Replies
2. UNIX for Advanced & Expert Users
Does know where I can find what ALL of the set options do in vi? I can't find it anywhere in vi's man pages or help files. I know about :set all but a lot of the options I have no clue what they do. (3 Replies)
Discussion started by: cokedude
3 Replies
3. Shell Programming and Scripting
I'm a beginner in shell scripting (I'm using ksh). I'm manipulating some files and I'm using set -A to transform each read line into a numeric array.
However, inside the 'for' loop the options of set (ie '-A') are not recognized (the vi editor doesn't highlight it and it doesn't work).
Where... (4 Replies)
Discussion started by: kasumlolla
4 Replies
4. UNIX for Dummies Questions & Answers
I'm reading about debugging aids in bash and have come across the set command. It says in my little book that an addition to typing
set
you can also use them "on the command line when running a script..." and it lists this in a small table:
set -o option Command Line... (5 Replies)
Discussion started by: Straitsfan
5 Replies
5. Shell Programming and Scripting
Hi all,
I need a script to delete a large set of files from a directory under / based on an input file and want to redirect errors into separate file.
I have already prepared a list of files in the input file.
Kndly help me.
Thanks,
Prash (36 Replies)
Discussion started by: prash358
36 Replies
6. HP-UX
Hi Experts,
Need your help in understanding the commands to setup the environment variables in hp-ux.
Beleive need to use either set,setenv or export.
I am confused between above three options, when to use which option?
On command line, I have tried both set and setenv but couldn't... (7 Replies)
Discussion started by: userexperience
7 Replies
7. Shell Programming and Scripting
Hello!
I have quite a bit of map data that I have to edit. I originally had a DOS script that would reverse x1, y1 coordinates in order to change the direction of a particular segment in a map file. It worked wonderfully and all was well, but my bossman told me that there is a boatload of nodes... (9 Replies)
Discussion started by: Mothra
9 Replies
8. Programming
Hi All,
We are trying to replace a 3rdparty where we don't know how they handled the reader part here. The query below is getting 197 * 2038017 row in the table.
In the below code we are trying to run the query and execute in the DB part and fetch and read the record. That is where it is... (1 Reply)
Discussion started by: arunkumar_mca
1 Replies
LEARN ABOUT SUSE
mount.crypt
mount.crypt(8) pam_mount mount.crypt(8)
Name
mount.crypt - mount a dm-crypt encrypted volume
Syntax
mount.crypt [-nrv] [-o options] device directory
Options
-o options
Set further mount options. mount.crypt will take out its own options it recognizes and passes any remaining options on to the under-
lying mount program. See below for possible options.
-n Do not update /etc/mtab. Note that this makes it impossible to unmount the volume by naming the container - you will have to pass
the mountpoint to umount.crypt.
-r Set up the loop device (if necessary) and crypto device in read-only mode. (The mount itself will necessarily also be read-only.)
Note that doing a remount using `mount /mnt -o remount,rw` will not make the mount readwrite. The crypto and loop devices will have
to be disassociated first.
-v Turn on debugging and be a bit more verbose.
Mount options
cipher The cryptsetup cipher used for the encrypted volume. This option is mandatory. pmt-ehd(8) defaults to creating volumes with
"aes-cbc-essiv:sha256" as a cipher.
dm-timeout=seconds
Wait at most this many seconds for udev to create /dev/mapper/name after calling cryptsetup(8). The default value is 0 seconds.
fsck Run fsck on the container before mounting it.
fsk_cipher
The OpenSSL cipher used for the filesystem key.
fsk_hash
The OpenSSL hash used for producing key and IV.
fstype The exact type of filesystem in the encrypted container. The default is to let the kernel autodetect.
keyfile
The path to the key file. This option is mandatory for "normal" crypto volumes and should not be used for LUKS volumes.
remount
Causes the filesystem to be remounted with new options. Note that mount.crypt cannot switch the underlying loop device (if applies)
or the crypto device between read-only and read-write once it is created; only the actual filesystem mount can be changed, with lim-
its. If the loop device is read-only, the crypto device will be read-only, and changing the mount to read-write is impossible. Sim-
ilarly, going from rw to ro will only mark the mount read-only, but not the crypto or loop device, thus making it impossible to set
the filesystem the crypto container is located on to read-only.
ro Same as the -r option.
verbose
Same as the -v option.
Obsolete mount options
This section is provided for reference.
loop This option used to set up a loop device, because cryptsetup(8) expects a block device. The option is ignored because mount.crypt
can figure this out on its own.
pam_mount 2008-10-08 mount.crypt(8)