PFS downgrade problem

[Tim Darby]

And this is what I got this morning:

# hammer pfs-downgrade /mnt/pfs/test

pfs-downgrade of PFS#2 () succeeded

I hadn't done anything more to it yesterday, but did leave it mounted
overnight.  Is it possible that the nightly scheduled hammer maintenance
script cleaned up something that fixed the problem?


Tim


On Tue, Nov 26, 2013 at 1:07 AM, Tim Darby <t+dfbsd at timdarby.net> wrote:

> I tried to downgrade a master PFS and got this:
>
> # hammer pfs-downgrade /mnt/pfs/test
>
> pfs-upgrade of PFS#2 () failed: Directory not empty
>
> There shouldn't have been any processes using that PFS but, just to be
> sure, I rebooted the machine and tried again with the same result.  Just
> for the fun of it, I tried this:
>
> # hammer pfs-upgrade /mnt/pfs/test
>
> pfs-upgrade of PFS#2 () failed: Directory not empty
> ​As far as I know, this PFS is good and I was able to mirror copy it to
> another PFS successfully.  Also, unrelated, but I find it a little odd that
> if you try to upgrade a master, you get an upgrade succeeded message,
> instead of "PFS is already a master".​
>
> ​I'm on v3.7.1.38.g703b85-DEVELOPMENT, but this PFS was created at least
> a year ago and I haven't really done very much to it, other than add some
> files.  If I create a new master PFS and downgrade it, it works.​
>
>
> Tim
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20131126/7306e642/attachment-0002.html>