Hello,
Thanks for the reply first of all.
All ended up well in the end.
Indeed "mkdir /usr/ports && cd /usr/ports && portsnap extract" fixed the issue.
Disk space is not a problem, this is the status after(!) extracting ports tree:
Code:
[root@virtbsd91 ~]# df -m
Filesystem 1M-blocks Used Avail Capacity Mounted on
/dev/ada0p2 9905 5740 3372 63% /
devfs 0 0 0 100% /dev
I think the main problem (root cause) was a / filesystem corruption I had 1 week ago, that prevented me to boot. I fixed it with fsck /dev/ada0p2 but without using journal. After fsck fix, system booted up, but it seems some index files required by portsnap were deleted.
With regards to the error messages that I've posted in the first post of this thread, this is the relevant section which seems to be the stopper for extracting the ports tree:
Code:
Extracting new files:
comm: /usr/ports/.portsnap.INDEX: No such file or directory
/usr/sbin/portsnap: cannot create /usr/ports/.portsnap.INDEX: No such file or directory
Anyway, after re-extracting the ports tree, all is OK like before. The database with installed packages was not affected, so I could just continue the ports update operation, like nothing happened.
And yes, again with regards to the errors, and as a final proof that a missing file was the issue, this is the current status:
Code:
[root@virtbsd91 ~]# ls -al /usr/ports/.portsnap.INDEX
-rw-r--r-- 1 root wheel 2107349 May 18 13:29 /usr/ports/.portsnap.INDEX
So: Problem solved!