You might try sorting the entries returned by readdir by inode number before
you stat them.This is a long-standing weakness in ext3/ext4, and it has to
do with how we added hashed tree indexes to directories in (a) a backwards
compatible way, that (b) was POSIX compliant with respect to
On Oct 10, 2011, at 7:18 AM, David Sterba wrote:
Resetting the UUID on btrfs isn't a quick-and-easy thing - you have to
walk the entire tree and change every object. We've got a bad-hack in
meego that uses btrfs-debug-tree and changes the UUID while it runs
the entire tree, but it's ugly as
On Apr 21, 2011, at 3:42 PM, Josef Bacik wrote:
+ case SEEK_DATA:
+ case SEEK_HOLE:
+ return -EINVAL;
}
Maybe we should be returning EOPNOTSUPP?
-- Ted
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to
On Dec 5, 2010, at 5:21 AM, Milan Broz wrote:
Which kernel? 2.6.37-rc?
Anyone seen this with 2.6.36 and the same dmcrypt patch?
(All info I had is that is is stable with here.)
It still seems to like dmcrypt with its parallel processing is just
trigger to another bug in 37-rc.
I've
On Nov 19, 2010, at 12:10 AM, Nick Piggin wrote:
But asynch writeout needs a mutex rather than refcount so the umount
has something to block against and not just fail.
Or we use a completion handler instead of a mutex for umount?
- Ted
--
To unsubscribe from this list: send the line
On Nov 18, 2010, at 3:18 AM, Nick Piggin wrote:
s_count just prevents it from going away, but s_umount is still needed
to keep umount, remount,ro, freezing etc activity away. I don't think
there is an easy way to do it.
Hmm what about encoding the fact that we are in the process of
On Aug 25, 2010, at 8:52 AM, Peter Zijlstra wrote:
Also, there's a good reason for disliking (a), its a deadlock scenario,
suppose we need to write out data to get free pages, but the writing out
is blocked on requiring free pages.
There's really nothing the page allocator can do to help
On Apr 26, 2010, at 6:18 AM, KOSAK
AOP_WRITEPAGE_ACTIVATE was introduced for ramdisk and tmpfs thing
(and later rd choosed to use another way).
Then, It assume writepage refusing aren't happen on majority pages.
IOW, the VM assume other many pages can writeout although the page can't.
Then,
On Fri, Jun 12, 2009 at 02:55:33PM -0700, Linus Torvalds wrote:
On Thu, 11 Jun 2009, Chris Mason wrote:
Existing filesystems will be upgraded to the new format on the first
mount. All of your old data will still be there and still work
properly, but I strongly recommend a full backup
On Wed, Jan 28, 2009 at 11:01:57AM -0500, Bill Nottingham wrote:
Bill Nottingham (nott...@redhat.com) said:
btrfs requires version 0.18 of its tools, and squashfs requires
4.0.
This time, with a typo fix.
While you're at it, could you also update e2fsprogs to require 1.41.4.
It's
On Fri, Jan 09, 2009 at 07:55:09PM +0100, Andi Kleen wrote:
But _users_ just get their oopses sent automatically. So it's not about
If they send it from distro kernels the automated oops sender could
just fetch the debuginfo rpm and decode it down to a line.
My old automatic user segfault
I'm beginning to think that for the kernel, we should just simply
remove CONFIG_OPTIMIZE_INLINING (so that inline means
always_inline), and -fno-inline-functions
-fno-inline-functions-called-one (so that gcc never inlines functions
behind our back) --- and then we create tools that count how many
On Fri, Aug 15, 2008 at 01:52:52PM -0400, Chris Mason wrote:
Have you tried this one:
http://article.gmane.org/gmane.linux.file-systems/25560
This bug should cause fragmentation on small files getting forced out
due to memory pressure in ext4. But, I wasn't able to really
demonstrate it
13 matches
Mail list logo
