My mistake, I'd assumed (yes I know the implications of that word)
that this was on an NFS mount point. the rsize attribute only pertains
to NFS mounted filesystems
-C
2009/2/4 Randy Brown :
> I'm having trouble getting the file system to mount after adding the rsize
> parameter. Here is my fsta
I'm having trouble getting the file system to mount after adding the
rsize parameter. Here is my fstab entry:
/dev/vgdevl/shared /fs/sharedgfs defaults0 0
I changed it to:
/dev/vgdevl/shared /fs/sharedgfs
defaults,rsize=81920 0
an
Great. Thanks. I'll give that a shot. I just need to find umount and
mount that file system to see if it worked.
Randy
Corey Kovacs wrote:
I had a similar problem. Reducing my rsize back to 8k from 32k fixed
it. Problem root was the lock files in the .qt directory.
Regards,
Corey
On Fe
I had a similar problem. Reducing my rsize back to 8k from 32k fixed
it. Problem root was the lock files in the .qt directory.
Regards,
Corey
On Feb 4, 2009, at 16:00, Randy Brown wrote:
We are seeing a very strange issue with KDE with all kernels later
than 2.6.18-53.1.21 on our cluster
We are seeing a very strange issue with KDE with all kernels later than
2.6.18-53.1.21 on our cluster nodes. When users attempt to log into the
machine using KDE, it never makes it to the KDE splash screen. The
machine just hangs on a solid blue screen. I can then restart the
Xserver and log
