kern/177985: [zfs] disk usage problem when copying from one zfs dataset to another on the same pool using mv command
Jon
sybersnake at gmail.com
Sat Apr 20 19:50:01 UTC 2013
The following reply was made to PR kern/177985; it has been noted by GNATS.
From: Jon <sybersnake at gmail.com>
To: Andriy Gapon <avg at FreeBSD.org>
Cc: "bug-followup at FreeBSD.org" <bug-followup at FreeBSD.org>
Subject: Re: kern/177985: [zfs] disk usage problem when copying from one zfs dataset to another on the same pool using mv command
Date: Sat, 20 Apr 2013 15:49:41 -0400
This is not a bug, it is a workflow problem introduced by the difference in b=
ehavior between ZFS datasets and fixed sized file systems.=20
You should be able to move files from one dataset to another on the same poo=
l without having to copy it to another pool and back. This all can be accomp=
lished by deleting copied files more often than it currently does or at leas=
t adding a flag to turn on synchronized deletes.
After I am done testing the same scenario on Solaris I will run the test Ste=
ve suggested.=20
Sent from my iPhone
On Apr 20, 2013, at 3:12 PM, Andriy Gapon <avg at FreeBSD.org> wrote:
>=20
> Sorry, but I do not see any bug reported here.
> mv behaves as it is expected/documented to behave.
> ZFS behaves as it should as well.
> If the behavior is surprising to you then please update your knowledge of t=
he tools.
> If you need a different behavior then you can script it yourself or use
> different tools to accomplish your job.
>=20
> --=20
> Andriy Gapon
More information about the freebsd-fs
mailing list