X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7B2AD.488627C0@onstor-exch02.onstor.net>; Tue, 19 Jun 2007 12:06:11 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: Too large mtime/atime on NFS volume
Date: Tue, 19 Jun 2007 12:06:11 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E04360C2F@onstor-exch02.onstor.net>
In-Reply-To: <20070619130522.6c1eb1e2@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Too large mtime/atime on NFS volume
Thread-Index: AceyrSrm339f4cOeRbip2G8KLVRpHgAABQRg
From: "Eric Barrett" <eric.barrett@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

My guess would be yes, but it would only be a guess.  Solaris 8 will do
NFS v3 unless you ask for v2.  Good question for Irie-san though.

=20

-----Original Message-----
From: Andy Sharp=20
Sent: Tuesday, June 19, 2007 1:05 PM
To: Eric Barrett
Subject: Re: Too large mtime/atime on NFS volume

Do we know if they are mounting it with nfsv3?

On Tue, 19 Jun 2007 11:55:24 -0700 "Eric Barrett"
<eric.barrett@onstor.com> wrote:

> Those numbers are exactly 2^31.  I'm sure that's significant, but I'm
> not sure what it means...
>=20
>=20
> > _____________________________________________=20
> > From: 	Shin Irie =20
> > Sent:	Tuesday, June 19, 2007 3:18 AM
> > To:	dl-cstech
> > Subject:	Too large mtime/atime on NFS volume
> >=20
> > Hi,
> >=20
> > I have a customer who cannot access to files on ONStor volume via
> > NFS. He gets following errors depending on UNIX commands. He is
> > running Solaris 8.
> >=20
> > cannot stat
> > Value too large for defined data type
> >=20
> > I found that mtime and atime is too large for UNIX (see attachment).
> > It is a mystery why these values were set because this volume is
> > only for NFS. No CIFS share is configured.
> >=20
> >  << File: large_mtime.jpg >>=20
> > I tried the touch command to modify mtime and atime, but it also got
> > "cannot stat" error.
> >=20
> > Does anyone have any idea how to modify mtime/atime, other than
> > creating a CIFS share to mdify the file from a CIFS client?
> >=20
> > --
> > Irie
> >=20
