Re: Possible issue with vnd

[David Brownlee <abs%absd.org@localhost>]

On 30 April 2017 at 19:52, D'Arcy Cain <darcy%netbsd.org@localhost> wrote:
> I can't cut and paste the commands I did but I think that the following is
> accurate.
>
> # dd if=/dev/zero of=xubuntu bs=1 seek=100g count=1
> # mke2fs xubuntu (from pkgsrc)
> # vndconfig -l (to get an available slot)
> # mount_ext2fs /dev/vnd2a /mnt
> # rsync -av -S ./Xubuntu/ /mnt/ (sync my built up file system)
>
> Is there anything in that list of commands that should have hung the system
> so badly that a reset button restart won't even boot?  I have to turn the
> system off for a few minutes first.
>
> I had this happen twice on one server and suspected the drives so I tried it
> on another and the same thing happened.  It seems to happen while copying a
> large, sparse file over.  Is the fact that the source file and target file
> system are both sparse causing the problem?
>
> Running a recently compiled 7.1.0_PATCH kernel and userland.

I'm wondering if its hung of it its hit some pathological filesystems
(wapl?) case which is taking an excessive time, but not entirely hung.
Might be interesting to see if a smaller value works (says the man not
immediately trying it on his box :)

David