11-12-2009
FWIW, we use EXT3 and it works fine.
8 More Discussions You Might Find Interesting
1. Solaris
Hi,
Does solaris support the XFS file sytems?
If so, how can I mount a shared directory from another machine (which is using XFS)?
thanks (3 Replies)
Discussion started by: orahi001
3 Replies
2. Filesystems, Disks and Memory
Gidday,
Are you using ext4 for production system? Or is it better to opt for a more
conservative strategy, like ext3 for instance?
What are your experiences?
Thanks in advance,
Loïc. (3 Replies)
Discussion started by: Loic Domaigne
3 Replies
3. UNIX for Advanced & Expert Users
Hi!
I created filesystem XFS on partition hda8 with subvolume real-time on partition hda5:
mkfs.xfs -r rtdev=/dev/hda5 /dev/hda8 and i mounted it:
mount -t xfs -o rtdev=/dev/hda5 /dev/hda8 /xfs
But I don't know how can I use this partition hda5 with subvolume real-time. I don't know how to... (3 Replies)
Discussion started by: Cadi2108
3 Replies
4. Linux
Hey everyone. I am in the process of setting up an iSCSI SAN to function as a log storage device for a number of servers. All of the initiators see the volume, and originally I formatted it with ext3 and went on my merry way. However after some research I'm having concerns that I should nuke the... (1 Reply)
Discussion started by: msarro
1 Replies
5. SuSE
Hello,
we got a MD3000i used as a network share between two servers (say A and B). The problem we are facing is that file/directories created by server A are not visible on server B (and viceversa). It's not a problem with permission (chmod 777 doesn't help).
The MD3000i was at first used ony... (0 Replies)
Discussion started by: neutrino
0 Replies
6. Red Hat
Hey everyone.
I am going to be using XFS for a project coming up. We're running RHEL 5.5. Simply typing
modprobe xfs
works just fine. The kernel module loads without any issue. Is there any issue with doing this and inserting "modprobe xfs" into /etc/rc.modules?
Is there a major reason to... (0 Replies)
Discussion started by: msarro
0 Replies
7. Red Hat
Is there any way to conver ext4 to ext3 filesystem without formatting the partition/disk ..
Had ext3 filesystem and had converted it to ext4 by issuing following command
# tune2fs -O extents,uninit_bg,dir_index /dev/sda1
# fsck -pf /dev/sda1
# blkid /dev/sda1
/dev/sda1:... (1 Reply)
Discussion started by: Shirishlnx
1 Replies
8. UNIX for Advanced & Expert Users
I have a RHEL6 VM that requires the use of remote storage using iSCSI and XFS for the mount point. Here's the issue:
With XFS you can't use the _netdev option for your mount point (pause for network) so my mount point doesn't mount properly because the network isn't up yet. I've moved the... (3 Replies)
Discussion started by: ksfolsom
3 Replies
LEARN ABOUT LINUX
qmail-command
qmail-command(8) System Manager's Manual qmail-command(8)
NAME
qmail-command - user-specified mail delivery program
SYNOPSIS
in .qmailext: |command
DESCRIPTION
qmail-local will, upon your request, feed each incoming mail message through a program of your choice.
When a mail message arrives, qmail-local runs sh -c command in your home directory. It makes the message available on command's standard
input.
WARNING: The mail message does not begin with qmail-local's usual Return-Path and Delivered-To lines.
Note that qmail-local uses the same file descriptor for every delivery in your .qmail file, so it is not safe for command to fork a child
that reads the message in the background while the parent exits.
EXIT CODES
command's exit codes are interpreted as follows: 0 means that the delivery was successful; 99 means that the delivery was successful, but
that qmail-local should ignore all further delivery instructions; 100 means that the delivery failed permanently (hard error); 111 means
that the delivery failed but should be tried again in a little while (soft error).
Currently 64, 65, 70, 76, 77, 78, and 112 are considered hard errors, and all other codes are considered soft errors, but command should
avoid relying on this.
ENVIRONMENT VARIABLES
qmail-local supplies several useful environment variables to command. WARNING: These environment variables are not quoted. They may con-
tain special characters. They are under the control of a possibly malicious remote user.
SENDER is the envelope sender address. NEWSENDER is the forwarding envelope sender address, as described in dot-qmail(5). RECIPIENT is
the envelope recipient address, local@domain. USER is user. HOME is your home directory, homedir. HOST is the domain part of the recipi-
ent address. LOCAL is the local part. EXT is the address extension, ext.
HOST2 is the portion of HOST preceding the last dot; HOST3 is the portion of HOST preceding the second-to-last dot; HOST4 is the portion of
HOST preceding the third-to-last dot.
EXT2 is the portion of EXT following the first dash; EXT3 is the portion following the second dash; EXT4 is the portion following the third
dash. DEFAULT is the portion corresponding to the default part of the .qmail-... file name; DEFAULT is not set if the file name does not
end with default.
DTLINE and RPLINE are the usual Delivered-To and Return-Path lines, including newlines. UFLINE is the UUCP-style From_ line that qmail-
local adds to mbox-format files.
SEE ALSO
dot-qmail(5), envelopes(5), qmail-local(8)
qmail-command(8)