ronnie sahlberg posted on Sat, 21 Dec 2013 17:15:33 -0800 as excerpted:
Similar things happened to me. (See my unanswered posts ~1Sep, this fs
is not really ready for production I think)
No I think about that one. Known fact. Btrfs is not yet fully stable
and is still under heavy
Hi!
Today I started my backup script which rsync´s my system to an external 3,5
inch 2 TB harddisk with the wrong destination dir which I notices more than
150 GiB of data has been copied twice instead of diffing with an existing
subvolume.
Thus I rm -rf the misplaced backup and started the
On Sat, Dec 21, 2013 at 08:07:51PM +0300, Vyacheslav Dubeyko wrote:
-static int can_set_xattr(struct inode *inode, const char *name,
- const void *value, size_t value_len)
This function works for all handlers. So, I don't think that it makes sense
to delete it.
On fri, 20 Dec 2013 05:30:48 -0800, Josef Bacik wrote:
On 12/19/2013 07:08 PM, Qu Wenruo wrote:
I'm sorry but I failed to reproduce the problem.
Btrfs/012 in xfstests has been run for serveral hours but nothing
happened.
Would you please give me some more details about the environment or
Hello,
I ran dmesg and saw a bunch of these:
[564421.874063] BTRFS debug (device sda2): unlinked 32 orphans
[568021.386733] BTRFS debug (device sda2): unlinked 32 orphans
[569943.269610] BTRFS debug (device sda2): unlinked 32 orphans
[570929.840278] BTRFS debug (device sda2): unlinked 32 orphans
On Sun, 2013-12-22 at 11:28 -0800, Christoph Hellwig wrote:
- if (!strncmp(name, XATTR_MAC_OSX_PREFIX, XATTR_MAC_OSX_PREFIX_LEN)) {
- /*
- * This makes sure that we aren't trying to set an
- * attribute in a different namespace by prefixing it
-
