Thanks for tracking this down. Since other uses of store_create expect it
to consume the port on success and not on failure, I changed dlabel.c to do
likewise. The comment describing store_create is not entirely clear.
___
Bug-hurd mailing list
[EMAIL
Roland McGrath <[EMAIL PROTECTED]> writes:
> [...] Some call somewhere either clobbers the _hurd_fd[fd] data
> structure, or consumes the send right. With these techniques, you
> should be able to tell which and where.
Thanks for your helpful advice; fd_get_device() in `dlabel.c' -- this
file i
> > First you can try "trap '' SIGLOST" to ignore the signal [...]
>
> ... `mkfs.ufs' tells me about a `(ipc/send) invalid destination port',
> when SIGLOST is trapped.
Ok. That's what I was expecting. The details of the message you looked at
don't tell you anything without examining the port
Roland McGrath <[EMAIL PROTECTED]> writes:
> [...] As to the SIGLOST crash, that is kind of strange. That error
> is supposed to indicate that the RPC server appeared to die, in this
> case the storeio or filesystem.
Storeio keeps running, but ...
> First you can try "trap '' SIGLOST" to ign
Note that the ufs filesystem has not been used much at all in a long time
and has not gotten nearly as much real-world testing as ext2fs, so there
may be more bugs.
As to the uid of the root dir, that seems reasonable enough. On the Hurd
it seems most sane to have mkfs.ufs do whatever mke2fs doe
Hello,
I am new to hurd and just tried to use `mkfs.ufs' to create an UFS on
a local partition. I am running a Hurd system from the Debian
hurd_20011105 package.
I expierienced that `mkfs.ufs' fails after printing the superblock
locations with a `Resource lost' error. After some investigation I
