> On Thu, Jan 25, 2001 at 02:18:01PM -0800, Matthew Jacob wrote:
> > An update on this
> >
> > If the server is Solaris, neither NetBSD nor FreeBSD (i386 or alpha) have a
> > problem (as clients).
> >
> > The problem is therefore in some interaction between this server (see
> > http://ww
On Thu, Jan 25, 2001 at 02:18:01PM -0800, Matthew Jacob wrote:
> An update on this
>
> If the server is Solaris, neither NetBSD nor FreeBSD (i386 or alpha) have a
> problem (as clients).
>
> The problem is therefore in some interaction between this server (see
> http://www.traakan.com- sort
> VLF-incapable utilities. (on a related note, is there a need for
> vlfread()/vlfwrite() in the BSD's, or is VLF support native in the read/write
> calls?
The standard off_t is 64 bits in all of the BSDs.
--
... every activity meets with opposition, everyone who acts has his
rivals and unfo
> knowing NFS in general far better than *BSD in specific, I would guess the best
> thing to do (if you suspect server/client communication anomaly) is to grab a
> snoop/tcpdump of the failure. I'm trying to think of a clever way to cause the
> failure immediately, so you're not tracing 4GB of w
* Nathan Parrish <[EMAIL PROTECTED]> [010125 13:19] wrote:
> knowing NFS in general far better than *BSD in specific, I would guess the best
> thing to do (if you suspect server/client communication anomaly) is to grab a
> snoop/tcpdump of the failure. I'm trying to think of a clever way to cause
knowing NFS in general far better than *BSD in specific, I would guess the best
thing to do (if you suspect server/client communication anomaly) is to grab a
snoop/tcpdump of the failure. I'm trying to think of a clever way to cause the
failure immediately, so you're not tracing 4GB of writes...
>
> Matthew Jacob writes:
> >
> > Same code compiled on Solaris is happy.
>
> Perhaps there's some braindamage in it. I'm afraid of something like:
>
> #ifdef Solaris
> typedef filefoo u_int64_t;
> #else
> typedef filefoo u_int32_t;
> #endif
>
I'll try with dd then,... let y'all know...
Matthew Jacob writes:
>
> Same code compiled on Solaris is happy.
Perhaps there's some braindamage in it. I'm afraid of something like:
#ifdef Solaris
typedef filefoo u_int64_t;
#else
typedef filefoo u_int32_t;
#endif
;)
Drew
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubs
On Thu, 25 Jan 2001, Andrew Gallatin wrote:
>
> Matthew Jacob writes:
> >
> > I came across an embarrassing comparison last night-
> >
> > FreeBSD NFS clients (well, i386) stop writing files at 4GB.
> >
> > Solaris, with O_LARGEFILE options in the open arguments, does not.
> >
> > Do
Matthew Jacob writes:
>
> I came across an embarrassing comparison last night-
>
> FreeBSD NFS clients (well, i386) stop writing files at 4GB.
>
> Solaris, with O_LARGEFILE options in the open arguments, does not.
>
> Does anyone here know what FreeBSD ought to be doing about this?
>
> > But I won't let it go! I was hoping to replace my Solaris box with either
> > FreeBSD or NetBSD as my main home directory server. FreeBSD 4.2 panics part
> > way through the first LADDIS runs I was using to test it with and I can't get
> > NetBSD to start as a LADDIS client (I hadn't got the
* Matthew Jacob <[EMAIL PROTECTED]> [010125 09:18] wrote:
>
>
> On Thu, 25 Jan 2001, Dan Nelson wrote:
>
> > In the last episode (Jan 25), Matthew Jacob said:
> > > On Thu, 25 Jan 2001, Dan Nelson wrote:
> > > > Make sure you're using NFSv3 mounts (should be the default, but if not,
> > > > add
On Thu, 25 Jan 2001, Dan Nelson wrote:
> In the last episode (Jan 25), Matthew Jacob said:
> > On Thu, 25 Jan 2001, Dan Nelson wrote:
> > > Make sure you're using NFSv3 mounts (should be the default, but if not,
> > > add "nfsv3" to the options column in fstab). I cross-mount FreeBSD,
> > > Tr
To be fair, I should say that the server is a 'specical' box.
But an lmdd writing to a file in 250GB partition that I started from Solaris
last night is still going. The NetBSD && FreeBSD writes both stopped at 4GB. I
suppose it still could be the server, but, well, it's hard to sell against
som
In the last episode (Jan 25), Matthew Jacob said:
> On Thu, 25 Jan 2001, Dan Nelson wrote:
> > Make sure you're using NFSv3 mounts (should be the default, but if not,
> > add "nfsv3" to the options column in fstab). I cross-mount FreeBSD,
> > Tru64, and Solaris boxes via NFS and can access large
On Thu, 25 Jan 2001, Dan Nelson wrote:
> In the last episode (Jan 25), Matthew Jacob said:
> > I came across an embarrassing comparison last night-
> >
> > FreeBSD NFS clients (well, i386) stop writing files at 4GB.
> >
> > Solaris, with O_LARGEFILE options in the open arguments, does not.
> >
In the last episode (Jan 25), Matthew Jacob said:
> I came across an embarrassing comparison last night-
>
> FreeBSD NFS clients (well, i386) stop writing files at 4GB.
>
> Solaris, with O_LARGEFILE options in the open arguments, does not.
>
> Does anyone here know what FreeBSD ought to be doin
I came across an embarrassing comparison last night-
FreeBSD NFS clients (well, i386) stop writing files at 4GB.
Solaris, with O_LARGEFILE options in the open arguments, does not.
Does anyone here know what FreeBSD ought to be doing about this?
Or have I missed something? There is no O_LARGEFI
18 matches
Mail list logo
