Mikhail T. wrote:
> On 28.11.2015 17:41, Jilles Tjoelker wrote:
> > Although cp -R will normally copy a fifo by calling mkfifo at the
> > destination, it may open one if a regular file is replaced with a fifo
> > between the time it reads the directory and it copies that file.
>
> The sole fifo
Mikhail T. wrote:
> On 28.11.2015 17:41, Jilles Tjoelker wrote:
> > Although cp -R will normally copy a fifo by calling mkfifo at the
> > destination, it may open one if a regular file is replaced with a fifo
> > between the time it reads the directory and it copies that file.
>
> The sole fifo
On Sat, Nov 28, 2015 at 10:42:28AM -0500, Mikhail T. wrote:
> I was copying /home from an old server (narawntapu) to a new one
> (aldan). The narawntapu:/home is mounted on aldan as /mnt with flags
> ro,intr. On narawntapu /home was simply located on an SSD, but on aldan
> I created a ZFS
quot;fifoor" -- does this
point to a trouble in the ZFS, the NFS-client, or the NFS-server? Both
systems run FreeBSD/amd64 of recent 10.x-vintage.
Thanks!
-mi
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinf
> 0xf80086231930: Listen queue overflow: 8 already in queue
> awaiting acceptance (57 occurrences)
> Nov 28 10:32:46 narawntapu kernel: sonewconn: pcb
> 0xf80086231930: Listen queue overflow: 8 already in queue
> awaiting acceptance (68 occurrences)
>
>
On Sat, Nov 28, 2015 at 10:42:28AM -0500, Mikhail T. wrote:
> I was copying /home from an old server (narawntapu) to a new one
> (aldan). The narawntapu:/home is mounted on aldan as /mnt with flags
> ro,intr. On narawntapu /home was simply located on an SSD, but on aldan
> I created a ZFS
Jilles Tjoelker wrote:
> On Sat, Nov 28, 2015 at 10:42:28AM -0500, Mikhail T. wrote:
> > I was copying /home from an old server (narawntapu) to a new one
> > (aldan). The narawntapu:/home is mounted on aldan as /mnt with flags
> > ro,intr. On narawntapu /home was simply located on an SSD, but on
On 28.11.2015 17:41, Jilles Tjoelker wrote:
> Although cp -R will normally copy a fifo by calling mkfifo at the
> destination, it may open one if a regular file is replaced with a fifo
> between the time it reads the directory and it copies that file.
The sole fifo under /home here was
on 30/01/2013 00:44 Andriy Gapon said the following:
on 29/01/2013 23:44 Hiroki Sato said the following:
http://people.allbsd.org/~hrs/FreeBSD/pool-20130130.txt
http://people.allbsd.org/~hrs/FreeBSD/pool-20130130-info.txt
[snip]
See tid 100153 (arc reclaim thread), tid 100105
Andriy Gapon wrote:
on 30/01/2013 00:44 Andriy Gapon said the following:
on 29/01/2013 23:44 Hiroki Sato said the following:
http://people.allbsd.org/~hrs/FreeBSD/pool-20130130.txt
http://people.allbsd.org/~hrs/FreeBSD/pool-20130130-info.txt
[snip]
See tid 100153 (arc reclaim
on 30/01/2013 01:06 Rick Macklem said the following:
Andriy Gapon wrote:
on 29/01/2013 23:44 Hiroki Sato said the following:
http://people.allbsd.org/~hrs/FreeBSD/pool-20130130.txt
http://people.allbsd.org/~hrs/FreeBSD/pool-20130130-info.txt
I recognize here a ZFS ARC deadlock that
Andriy Gapon wrote:
on 30/01/2013 01:06 Rick Macklem said the following:
Andriy Gapon wrote:
on 29/01/2013 23:44 Hiroki Sato said the following:
http://people.allbsd.org/~hrs/FreeBSD/pool-20130130.txt
http://people.allbsd.org/~hrs/FreeBSD/pool-20130130-info.txt
I recognize here a
Hiroki Sato h...@freebsd.org wrote
in 20130104.023244.472910818423317661@allbsd.org:
hr Konstantin Belousov kostik...@gmail.com wrote
hr in 20130102174044.gb82...@kib.kiev.ua:
hr
hr ko I might take a closer look this evening and see if I can spot anything
hr ko in the log, rick
hr ko
on 29/01/2013 23:44 Hiroki Sato said the following:
http://people.allbsd.org/~hrs/FreeBSD/pool-20130130.txt
http://people.allbsd.org/~hrs/FreeBSD/pool-20130130-info.txt
I recognize here a ZFS ARC deadlock that should have been prevented by r241773
and its MFCs (r242858 for 9, r242859 for
Andriy Gapon wrote:
on 29/01/2013 23:44 Hiroki Sato said the following:
http://people.allbsd.org/~hrs/FreeBSD/pool-20130130.txt
http://people.allbsd.org/~hrs/FreeBSD/pool-20130130-info.txt
I recognize here a ZFS ARC deadlock that should have been prevented by
r241773
and its MFCs
Rick Macklem rmack...@uoguelph.ca wrote
in 1914428061.1617223.1357133079421.javamail.r...@erie.cs.uoguelph.ca:
rm Hiroki Sato wrote:
rm Hello,
rm
rm I have been in a trouble about my NFS server for a long time. The
rm symptom is that it stops working in one or two weeks after a boot. I
rm
Konstantin Belousov kostik...@gmail.com wrote
in 20130102174044.gb82...@kib.kiev.ua:
ko I might take a closer look this evening and see if I can spot anything
ko in the log, rick
ko ps: I hope Alan and Kostik don't mind being added to the cc list.
ko
ko What I see in the log is that the lock
Hiroki Sato wrote:
Hello,
I have been in a trouble about my NFS server for a long time. The
symptom is that it stops working in one or two weeks after a boot. I
could not track down the cause yet, but it is reproducible and only
occurred under a very high I/O load.
It did not panic, just
On Wed, Jan 02, 2013 at 08:24:39AM -0500, Rick Macklem wrote:
Hiroki Sato wrote:
Hello,
I have been in a trouble about my NFS server for a long time. The
symptom is that it stops working in one or two weeks after a boot. I
could not track down the cause yet, but it is reproducible and
Hello,
I have been in a trouble about my NFS server for a long time. The
symptom is that it stops working in one or two weeks after a boot. I
could not track down the cause yet, but it is reproducible and only
occurred under a very high I/O load.
It did not panic, just stopped
Hiroki Sato h...@freebsd.org wrote:
I have been in a trouble about my NFS server for a long time.
The symptom is that it stops working in one or two weeks after
a boot ... It did not panic, just stopped working---while it
responded to ping, userland programs seemed not working ...
, 26 May 2009, Mike Andrews wrote:
Takahashi Yoshihiro wrote:
Today's stable has a problem creating a new file via NFS on ZFS.
On the NFS server, there is no problem.
% cd /ZFS
% mktemp hoge
hoge
% ls -l hoge
-rw--- 1 nyan nyan 0 5 26 19:09 hoge
But it's a problem on the NFS
On Tue, 9 Jun 2009, Attila Nagy wrote:
Hello,
I've also ran into it, it's a pretty killer feature. :-O
Any chance for us on the fix?
It's kern/135039, fyi.
___
freebsd-stable@freebsd.org mailing list
The flags checks are too strict. File a PR. I'll fix it when I get to
it. Sorrry.
-Kip
On Wed, May 27, 2009 at 7:24 PM, Mike Andrews mandr...@bit0.com wrote:
On Tue, 26 May 2009, Mike Andrews wrote:
Takahashi Yoshihiro wrote:
Today's stable has a problem creating a new file via NFS on ZFS
On Tue, 26 May 2009, Mike Andrews wrote:
Takahashi Yoshihiro wrote:
Today's stable has a problem creating a new file via NFS on ZFS.
On the NFS server, there is no problem.
% cd /ZFS
% mktemp hoge
hoge
% ls -l hoge
-rw--- 1 nyan nyan 0 5 26 19:09 hoge
But it's a problem on the NFS
Today's stable has a problem creating a new file via NFS on ZFS.
On the NFS server, there is no problem.
% cd /ZFS
% mktemp hoge
hoge
% ls -l hoge
-rw--- 1 nyan nyan 0 5 26 19:09 hoge
But it's a problem on the NFS client.
# mount server:/ZFS /ZFS
% cd /ZFS
% mktemp hoge
mktemp
Takahashi Yoshihiro wrote:
Today's stable has a problem creating a new file via NFS on ZFS.
On the NFS server, there is no problem.
% cd /ZFS
% mktemp hoge
hoge
% ls -l hoge
-rw--- 1 nyan nyan 0 5 26 19:09 hoge
But it's a problem on the NFS client.
# mount server:/ZFS /ZFS
% cd /ZFS
27 matches
Mail list logo
