Hi everyone,
The master branch of the btrfs unstable tree has some important btrfs
fixes:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable.git master
I was seeing very rare metadata corruptions during long stress runs, and
eventually tracked it down to two different races in th
2011年2月15日9:14 Tsutomu Itoh :
> Sano-san,
>
> (2011/02/14 22:57), Yoshinori Sano wrote:
>> 2011年2月14日8:57 Tsutomu Itoh :
>>> (2011/02/12 20:17), Yoshinori Sano wrote:
To make Btrfs code more robust, several return value checks where memory
allocation can fail are introduced. I use BUG_ON
Sano-san,
(2011/02/14 22:57), Yoshinori Sano wrote:
> 2011年2月14日8:57 Tsutomu Itoh :
>> (2011/02/12 20:17), Yoshinori Sano wrote:
>>> To make Btrfs code more robust, several return value checks where memory
>>> allocation can fail are introduced. I use BUG_ON where I don't know how
>>> to handle t
Excerpts from Marti Raudsepp's message of 2011-02-14 12:58:17 -0500:
> On Mon, Feb 14, 2011 at 17:01, Chris Mason wrote:
> > Or, it could just be delalloc ;)
>
> I suspect delalloc. After creating the file, filefrag reports "1
> extent found", but for some reason it doesn't actually print out
> d
On Mon, Feb 14, 2011 at 17:01, Chris Mason wrote:
> Or, it could just be delalloc ;)
I suspect delalloc. After creating the file, filefrag reports "1
extent found", but for some reason it doesn't actually print out
details of the extent.
After a "sync" call, the extent appears and "cp" starts wo
Excerpts from Andrew Lutomirski's message of 2011-02-11 19:35:02 -0500:
> On Fri, Feb 11, 2011 at 10:44 AM, Chris Mason wrote:
> > Excerpts from Andrew Lutomirski's message of 2011-02-11 10:08:52 -0500:
> >> As I type this, I have an ssh process running that's dumping data into
> >> a fifo at high
Excerpts from Josef Bacik's message of 2011-02-13 11:13:30 -0500:
> On Sun, Feb 13, 2011 at 06:07:36PM +0200, Marti Raudsepp wrote:
> > On Sun, Feb 13, 2011 at 17:57, Josef Bacik wrote:
> > > Does the same problem happen when you use cp --sparse=never?
> >
> > You are right. cp --sparse=never doe
On Sun, 13 Feb 2011 19:18:20 +
Hugo Mills wrote:
>Yes, it's the same piece of storage, just appearing at more than
> one point in your overall filesystem. Similar to the way that bind
> mounts work.
I've noticed that I can also rename subvolumes as well using mv(1).
Can I move/re-arrange
On Mon, Feb 14, 2011 at 3:59 AM, Zhong, Xin wrote:
> We build packages in a kvm-qemu chroot environment. And the root fs is btrfs.
> It hang during installing packages. And we found error message in dmesg:
>
> [ 84.320466] btrfs: use compression
> [ 288.711396] [ cut here ]
We build packages in a kvm-qemu chroot environment. And the root fs is btrfs.
It hang during installing packages. And we found error message in dmesg:
[ 84.320466] btrfs: use compression
[ 288.711396] [ cut here ]
[ 288.711569] kernel BUG at fs/btrfs/inode.c:6752!
[ 2
On Mon, Feb 14, 2011 at 12:41:46AM -0800, MOB wrote:
> So as I'm doing some maintenance on my personal video server, I'm noticing
> that when I'm copying files off of my btrfs partitions, they are getting
> larger...
>
> First partition is the original:
> http://pastebin.com/GM5xWetR
>
> I have
So as I'm doing some maintenance on my personal video server, I'm noticing that
when I'm copying files off of my btrfs partitions, they are getting larger...
First partition is the original:
http://pastebin.com/GM5xWetR
I have 3 affected partitions, This appears to have started with 2.6.37 but
12 matches
Mail list logo
