Sunil Mushran wrote:
On 04/22/2011 04:50 AM, Eric Blake wrote:
That blog also mentioned the useful idea of adding FIND_HOLE and
FIND_DATA, not implemented in Solaris, but which could easily be
provided as additional lseek constants in Linux to locate the start of
the next chunk without
(2011/04/22 21:45), David Sterba wrote:
Hi,
On Fri, Apr 22, 2011 at 06:05:40PM +0900, Tsutomu Itoh wrote:
It is necessary to unlock mutex_lock before it return an error when
btrfs_alloc_path() fails.
good catch! however I suggest to move the mutex_lock after the
allocation and check,
Hi, btrfs-progs patches for read only snapshots aren't in Chris
repository yet but btrfs already has support for that in place so,
someone forgot about this?
It appears that some new patches are coming to Chris btrfs-progs (new
tmp branch) so this was a nice opportunity to get those patches in.
On Thu, 21 Apr 2011 15:42:33 EDT, Josef Bacik said:
-SEEK_HOLE: this moves the file pos to the nearest hole in the file from the
given position.
Do we want the semantic to be the nearest hole? Or did we really want the
next hole? Loops like a bullet loaded in the chamber and pointed at the
On Tue, 19 Apr 2011 05:08:05 -0700 Chris Mason wrote:
Excerpts from Cheng Shao's message of 2011-04-18 17:49:29 -0400:
Hi there,
I'm periodically having issues with btrfs running in a Ubuntu VM using
VirtualBox. After the VM has been running for a while (a couple days),
any write
