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 mi/.licq/
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 al
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 filesyste
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 filesystem for it.
>
> The copying was started thu
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 filesystem for it.
The copying was started thus:
root@aldan:/home (435)
