Thanks for reaching out.
I'm primarily a Linux administrator and don't dabble much with HP-UX so if you need additional info, please let me know.
The HP-UX server is attached to EMC storage. Our Linux servers were previously backing up to a legacy Sun Solaris server but we've run out of space there so I'm trying to shift the scripts to now backup to the HP server. I've created the logical volume and filesystem from scratch. As mentioned, everything seems to be working as expected with the exception of using dump from Linux to this filesystem. The Linux servers are using the dump options "0uf". I've tried 0auf to no avail. Thanks again for reaching out.
- Bill
---------- Post updated at 12:11 PM ---------- Previous update was at 12:08 PM ----------
Keep in mind that the exact same script works flawlessly to both a Solaris server and another Linux server. As soon as I change one of the variables to point to the HP-UX server, it craps out after 2GB every time. The dump is over SSH. I've also tried RSH but got the same results. Thanks.
---------- Post updated at 12:20 PM ---------- Previous update was at 12:11 PM ----------
Proof that the filesystem in question does in fact support large files:
(I've also scp'd an 8GB file from the same Linux server to the filesystem)
Last edited by Scott; 11-09-2011 at 02:24 PM..
Reason: Code tags
I am working on HP-Unix.
I have a 600 MB file in compressed form.
During decompression, when file size reaches
2GB, decompression aborts.
What should be done? (3 Replies)
I want to have a permanent file created - and limit the size that this file can grow.. I want a circular file..
ie max size of file is 10 mb.. and if any new data written to file the oldest data removed..
How can I do this?
I am on solaris 9 x86 (3 Replies)
Can anybody help me?
How to increase file size limit in aix 5.2? I have already specified in /etc/security/limits file :
default:
fsize = -1
core = 2097151
cpu = -1
data = -1
rss = -1
stack = -1
nofiles = 2000 (2 Replies)
Hi,
I have a problem writing or copying a file 2GB or larger to either the second or third disk on my C8000. I've searched this forum and found some good information on this but still nothing to solve the problem.
I'm running hpux 11i, JFS3.3 and disk version 4 (from fstyp) on all 3 disks.
... (2 Replies)
Any idea how to get around this limit? I have a 42GB database backup file (.dmp) taking up disk space because neither tar nor cpio are able to put it onto a tape. I am on a SUN Solaris using SunOS 5.8. I would appreciate whatever help can be provided. Thanks! (9 Replies)
Hi All,
We are running HP rp7400 box with hpux 11iv1.
Recently, we changed 3 kernel parameters
a) msgseg from 32560 to 32767
b) msgmnb from 65536 to 65535
c) msgssz from 128 to 256
Then we noticed that all application debug file size increase upto 2GB then it stops. So far we did not... (1 Reply)
Hi All,
I want to store 32KB of file in Oracle DB into CLOB field. I am not able to insert more than 32KB of file into CLOB. So i want to put a limit on the file size. I am using k shell.
My file size will dynamically increase its size, i want to check the file size if it is more than 32KB... (1 Reply)
Hi,
Am trying to run zip -r on a 2.4G directory and it is failing with the error below. I believe this is because of the 2G limit of the zip program.
server101(oper01)/u01/temp$: date
Thu Mar 15 12:53:44 NZDT 2012
server101(oper01)/u01/temp$: ls -l
total 8
drwxr-x--x 4 oracle dba ... (1 Reply)
Discussion started by: newbie_01
1 Replies
LEARN ABOUT OPENSOLARIS
setfsgid
SETFSGID(2) Linux Programmer's Manual SETFSGID(2)NAME
setfsgid - set group identity used for filesystem checks
SYNOPSIS
#include <sys/fsuid.h>
int setfsgid(uid_t fsgid);
DESCRIPTION
The system call setfsgid() changes the value of the caller's filesystem group ID--the group ID that the Linux kernel uses to check for all
accesses to the filesystem. Normally, the value of the filesystem group ID will shadow the value of the effective group ID. In fact,
whenever the effective group ID is changed, the filesystem group ID will also be changed to the new value of the effective group ID.
Explicit calls to setfsuid(2) and setfsgid() are usually used only by programs such as the Linux NFS server that need to change what user
and group ID is used for file access without a corresponding change in the real and effective user and group IDs. A change in the normal
user IDs for a program such as the NFS server is a security hole that can expose it to unwanted signals. (But see below.)
setfsgid() will succeed only if the caller is the superuser or if fsgid matches either the caller's real group ID, effective group ID,
saved set-group-ID, or current the filesystem user ID.
RETURN VALUE
On both success and failure, this call returns the previous filesystem group ID of the caller.
VERSIONS
This system call is present in Linux since version 1.2.
CONFORMING TO
setfsgid() is Linux-specific and should not be used in programs intended to be portable.
NOTES
Note that at the time this system call was introduced, a process could send a signal to a process with the same effective user ID. Today
signal permission handling is slightly different. See setfsuid(2) for a discussion of why the use of both setfsuid(2) and setfsgid() is
nowadays unneeded.
The original Linux setfsgid() system call supported only 16-bit group IDs. Subsequently, Linux 2.4 added setfsgid32() supporting 32-bit
IDs. The glibc setfsgid() wrapper function transparently deals with the variation across kernel versions.
C library/kernel differences
In glibc 2.15 and earlier, when the wrapper for this system call determines that the argument can't be passed to the kernel without integer
truncation (because the kernel is old and does not support 32-bit group IDs), they will return -1 and set errno to EINVAL without attempt-
ing the system call.
BUGS
No error indications of any kind are returned to the caller, and the fact that both successful and unsuccessful calls return the same value
makes it impossible to directly determine whether the call succeeded or failed. Instead, the caller must resort to looking at the return
value from a further call such as setfsgid(-1) (which will always fail), in order to determine if a preceding call to setfsgid() changed
the filesystem group ID. At the very least, EPERM should be returned when the call fails (because the caller lacks the CAP_SETGID capabil-
ity).
SEE ALSO kill(2), setfsuid(2), capabilities(7), credentials(7)COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the
latest version of this page, can be found at https://www.kernel.org/doc/man-pages/.
Linux 2017-09-15 SETFSGID(2)