11-19-2009
I was told they did have it turned on. Basically at the time we started this layout we were the largest email system in the world (still are I think). The only we we had to handle the i/o load we were getting was small files and basically deep random directories. reiser was the only file system that could handle it. Red Hat assigned about 5 engineers to work with us and couldn't get ext close. They built us a custom gf2 after numerous attempts. It is now in the public release, I forget which ver.
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 DEBIAN
gfs2_grow
gfs2_grow(8) System Manager's Manual gfs2_grow(8)
NAME
gfs2_grow - Expand a GFS2 filesystem
SYNOPSIS
gfs2_grow [OPTION]... <DEVICE|MOUNTPOINT>...
DESCRIPTION
gfs2_grow is used to expand a GFS2 filesystem after the device upon which the filesystem resides has also been expanded. By running
gfs2_grow on a GFS2 filesystem, you are requesting that any spare space between the current end of the filesystem and the end of the device
is filled with a newly initialized GFS2 filesystem extension. When this operation is complete, the resource group index for the filesystem
is updated so that all nodes in the cluster can use the extra storage space that has been added.
You may only run gfs2_grow on a mounted filesystem; expansion of unmounted filesystems is not supported. You only need to run gfs2_grow on
one node in the cluster. All the other nodes will see the expansion has occurred and automatically start to use the newly available space.
You must be superuser to execute gfs2_grow. The gfs2_grow tool tries to prevent you from corrupting your filesystem by checking as many of
the likely problems as it can. When expanding a filesystem, only the last step of updating the resource index affects the currently
mounted filesystem and so failure part way through the expansion process should leave your filesystem in its original unexpanded state.
You can run gfs2_grow with the -T flag to get a display of the current state of a mounted GFS2 filesystem.
The gfs2_grow tool uses the resource group (RG) size that was originally calculated when mkfs.gfs2 was done. This allows tools like
fsck.gfs2 to better ensure the integrity of the file system. Since the new free space often does not lie on even boundaries based on that
RG size, there may be some unused space on the device after gfs2_grow is run.
OPTIONS
-D Print out debugging information about the filesystem layout.
-h Prints out a short usage message and exits.
-q Be quiet. Don't print anything.
-T Test. Do all calculations, but do not write any data to the disk and do not expand the filesystem. This is used to discover what the
tool would have done were it run without this flag.
-V Version. Print out version information, then exit.
BUGS
There is no way to shrink a GFS2 filesystem.
SEE ALSO
mkfs.gfs2(8) gfs2_jadd(8)
gfs2_grow(8)