Re: New data=ordered code pushed out to btrfs-unstable

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2008-07-18 at 16:09 -0400, Ric Wheeler wrote:

> Just to kick the tires, I tried the same test that I ran last week on 
> ext4. Everything was going great, I decided to kill it after 6 million 
> files or so and restart.
> 
> The unmount has taken a very, very long time - seems like we are 
> cleaning up the pending transactions at a very slow rate:
> 

This is a known problem, Yan will take care of it next week.  You've got
the right idea, cleaning old snapshots does more IO than it should.

The good news is that if you hit reset and mount again, it'll pick up
where it left off.  The bad news is it'll be be just as slow as last
time around ;)

> Jul 18 16:06:04 localhost kernel: cleaner awake
> Jul 18 16:06:04 localhost kernel: cleaner done
> Jul 18 16:06:34 localhost kernel: trans 188 in commit
> Jul 18 16:06:35 localhost kernel: trans 188 done in commit

And these I meant to get rid of

-chris


--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux