On 11/17/2014 09:52 PM, Peter wrote:
On 11/18/2014 02:50 PM, Fred Smith wrote:
But I don't think that's what I want. I want it to mount when the system
boots, but if for some reason it is not powered on, I don't want it to
hang up the whole boot process.
You want the nofail option.
Peter
On 11/19/2014 04:24 PM, Ted Miller wrote:
Didn't the nofail option disappear from Centos 7?
That would be news to me, and it would be a serious loss of
functionality if it did.
Peter
___
CentOS mailing list
CentOS@centos.org
Hi all!
I've got a Venus DS3R Pro2 external drive unit with two drives set up
as RAID-1, and the raid volume is formatted as ext4.
it is listed in /etc/fstab as:
UUID=f787c482-fb92-4ba7-87d6-cfeaef6b64c2 /mnt/backup ext4
defaults,users 0 2
if the external unit (which attaches via
On 2014-11-18, Fred Smith fre...@fcshome.stoneham.ma.us wrote:
I've got a Venus DS3R Pro2 external drive unit with two drives set up
as RAID-1, and the raid volume is formatted as ext4.
it is listed in /etc/fstab as:
UUID=f787c482-fb92-4ba7-87d6-cfeaef6b64c2 /mnt/backup ext4
On Mon, Nov 17, 2014 at 05:23:45PM -0800, Keith Keller wrote:
On 2014-11-18, Fred Smith fre...@fcshome.stoneham.ma.us wrote:
I've got a Venus DS3R Pro2 external drive unit with two drives set up
as RAID-1, and the raid volume is formatted as ext4.
it is listed in /etc/fstab as:
On November 17, 2014 7:50:27 PM CST, Fred Smith fre...@fcshome.stoneham.ma.us
wrote:
On Mon, Nov 17, 2014 at 05:23:45PM -0800, Keith Keller wrote:
On 2014-11-18, Fred Smith fre...@fcshome.stoneham.ma.us wrote:
I've got a Venus DS3R Pro2 external drive unit with two drives set
up
as RAID-1,
On 2014-11-18, Fred Smith fre...@fcshome.stoneham.ma.us wrote:
But I don't think that's what I want. I want it to mount when the system
boots, but if for some reason it is not powered on, I don't want it to
hang up the whole boot process.
noauto says it won't mount based on mount -a, and
On 11/18/2014 02:50 PM, Fred Smith wrote:
But I don't think that's what I want. I want it to mount when the system
boots, but if for some reason it is not powered on, I don't want it to
hang up the whole boot process.
You want the nofail option.
Peter
lheck...@users.sourceforge.net writes:
I would suspect the inode64 option is the problem
We had similar issues running 32 bit apps on a 64 bit clients accessing
'large' NFS servers (non-Linux NFS servers) - the 'fix' was to make sure
the file systems were exported/mounted with 32
lheck...@users.sourceforge.net wrote:
lheck...@users.sourceforge.net writes:
I would suspect the inode64 option is the problem
We had similar issues running 32 bit apps on a 64 bit clients accessing
'large' NFS servers (non-Linux NFS servers) - the 'fix' was to make sure
the file systems
It did not work. The test environemnt was set up wrong.
Is it possible to re-build the 32 bit application with large file support?
Nope.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
lheck...@users.sourceforge.net wrote:
It did not work. The test environemnt was set up wrong.
Is it possible to re-build the 32 bit application with large file support?
Nope.
I guess you might be out of luck?
I'm not sure you can safely mount an XFS file system without inode64
that was
We're experiencing problems with some legacy software when it comes to NFS
access. Even though files are visible in a terminal and can be accessed with
standard shell tools and vi, this software typically complains that the files
are empty or not syntactically correct.
The NFS filesystems
On 10/09/2012 02:16 PM, lheck...@users.sourceforge.net wrote:
The clients exhibiting the problem are running CentOS 5.4 and CentOS 5.8
x84_64.
Which NFS protocol version?
Have you tried NFS mount with vers=3 ?
Mogens
--
Mogens Kjaer, m...@lemo.dk
http://www.lemo.dk
Mogens Kjaer writes:
On 10/09/2012 02:16 PM, lheck...@users.sourceforge.net wrote:
The clients exhibiting the problem are running CentOS 5.4 and CentOS 5.8
x84_64.
Which NFS protocol version?
Have you tried NFS mount with vers=3 ?
From /proc:
nfs
lheck...@users.sourceforge.net wrote:
We're experiencing problems with some legacy software when it comes to NFS
access. Even though files are visible in a terminal and can be accessed with
standard shell tools and vi, this software typically complains that the files
are empty or not
I would suspect the inode64 option is the problem
We had similar issues running 32 bit apps on a 64 bit clients accessing
'large' NFS servers (non-Linux NFS servers) - the 'fix' was to make sure
the file systems were exported/mounted with 32 bit inode compatibility
17 matches
Mail list logo
