Am Samstag, 18. Oktober 2014, 18:32:49 schrieb Chris Samuel:
On Fri, 17 Oct 2014 02:09:30 PM Rich Freeman wrote:
Just for clarity - when can we expect to see these in the kernel?
The stable kernel rules say:
https://www.kernel.org/doc/Documentation/stable_kernel_rules.txt
# - It or an
inline as below.
On 10/17/2014 09:58 AM, Gui Hecheng wrote:
On Thu, 2014-09-04 at 20:02 +0800, Anand Jain wrote:
On 09/04/2014 05:58 PM, David Sterba wrote:
On Mon, Aug 18, 2014 at 04:38:18PM +0800, Anand Jain wrote:
ioctl BTRFS_IOC_FS_INFO return num_devices which does _not_ include
On Mon, 20 Oct 2014 10:01:56 AM Marc Dietrich wrote:
so fixes would be tagged earlier this way and merged automaticly.
I don't think there's a lot automatic about stable, Greg K-H merges patches
into a git tree here:
http://git.kernel.org/cgit/linux/kernel/git/stable/stable-queue.git
As you
On 10/20/2014 12:13 AM, Greg KH wrote:
On Sun, Oct 19, 2014 at 09:55:11PM +0200, Greg KH wrote:
On Sun, Oct 19, 2014 at 06:01:16AM -0400, Chris Mason wrote:
Hi everyone,
I've pulled out some of the btrfs commits from the merge window that
we'd like to see in stable. The full list of sha's
On Mon, Oct 20, 2014 at 04:38:28AM +, Duncan wrote:
Russell Coker posted on Sat, 18 Oct 2014 14:54:19 +1100 as excerpted:
# find . -name *546
./1412233213.M638209P10546 # ls -l ./1412233213.M638209P10546 ls: cannot
access ./1412233213.M638209P10546: No such file or directory
Does
On 2014-10-20 09:02, Zygo Blaxell wrote:
On Mon, Oct 20, 2014 at 04:38:28AM +, Duncan wrote:
Russell Coker posted on Sat, 18 Oct 2014 14:54:19 +1100 as excerpted:
# find . -name *546
./1412233213.M638209P10546 # ls -l ./1412233213.M638209P10546 ls: cannot
access
On Fri, Oct 17, 2014 at 08:17:37AM +, Hugo Mills wrote: On Fri, Oct 17,
2014 at 10:10:09AM +0200, Tomasz Torcz wrote:
On Fri, Oct 17, 2014 at 04:02:03PM +0800, Liu Bo wrote:
Recently I've observed some corruptions to systemd's journal
files which are somewhat puzzling. This is
On Mon, Oct 20, 2014 at 10:04 AM, Zygo Blaxell zblax...@furryterror.org wrote:
On Fri, Oct 17, 2014 at 08:17:37AM +, Hugo Mills wrote: On Fri, Oct 17,
2014 at 10:10:09AM +0200, Tomasz Torcz wrote:
On Fri, Oct 17, 2014 at 04:02:03PM +0800, Liu Bo wrote:
Recently I've observed some
Hi,
I'd like to calculate the compressed size of a btrfs filesystem. I read
the wiki and understand the backward compatibility issues mentioned.
Also, the df before and after method doesn't work for me and I have no
control over when end users are writing to the filesystem.
Wiki says
On Sun, Oct 19, 2014 at 7:13 PM, Greg KH gre...@linuxfoundation.org
wrote:
On Sun, Oct 19, 2014 at 09:55:11PM +0200, Greg KH wrote:
On Sun, Oct 19, 2014 at 06:01:16AM -0400, Chris Mason wrote:
Hi everyone,
I've pulled out some of the btrfs commits from the merge window
that
we'd
On Fri, Oct 17, 2014 at 04:02:03PM +0800, Liu Bo wrote:
Does scrub work for you?
Scrub ended with not errors:
scrub status for a4f339d4-c129-4485-acc1-1233d29c665d
scrub started at Fri Oct 17 10:04:24 2014 and finished after 31992
seconds
total bytes scrubbed: 6.03TiB with
On Thu, Oct 16, 2014 at 01:33:37PM +0200, David Sterba wrote:
I'd like to make it default with the 3.17 release of btrfs-progs.
Please let me know if you have objections.
For the record, 3.17 will not change the defaults. The timing of the
poll was very bad to get enough feedback before the
Hi,
the version 3.17 of btrfs-progs has been released.
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git v3.17
https://www.kernel.org/pub/linux/kernel/people/kdave/btrfs-progs/btrfs-progs-v3.17.tar.xz
Among other fixes and updates, there are many fsck improvements, most
On Mon, Oct 20, 2014 at 09:05:41AM -0700, Suman Chakravartula wrote:
I'd like to calculate the compressed size of a btrfs filesystem. I read
the wiki and understand the backward compatibility issues mentioned.
Also, the df before and after method doesn't work for me and I have no
control
On Sun, Oct 12, 2014 at 10:55:54PM +, Duncan wrote:
[...]
It's the raid-factor. =:^)
Btrfs in the kernel is apparently accounting for raid-factor in used
space in whatever function standard df is using, but not in available
space, even where that available space is already
On Fri, Oct 17, 2014 at 08:53:06AM -0400, Chris Mason wrote:
On Fri, Oct 17, 2014 at 4:54 AM, Tomasz Torcz to...@pipebreaker.pl wrote:
On Fri, Oct 17, 2014 at 04:29:36PM +0800, Liu Bo wrote:
On Fri, Oct 17, 2014 at 10:10:09AM +0200, Tomasz Torcz wrote:
On Fri, Oct 17, 2014 at 04:02:03PM
On Fri, Oct 17, 2014 at 11:01:51AM -0400, Chris Murphy wrote:
On Oct 16, 2014, at 5:17 AM, Tomasz Torcz to...@pipebreaker.pl wrote:
Broken files are in /var/log/journal directory. This directory
is set NOCOW with chattr, all the files within too.
Example of broken file:
On Fri, Oct 03, 2014 at 10:12:38AM -0700, Omar Sandoval wrote:
The RCU-friendly string API used internally by BTRFS is generic enough for
common use. This doesn't add any new functionality, but instead just moves the
code and documents the existing API.
Signed-off-by: Omar Sandoval
On 10/20/2014 07:37 PM, Robert White wrote:
On 10/18/2014 04:41 PM, Russell Coker wrote:
[...]
Also you said that you are using a 32bit user space copied from
another server under a 64bit kernel. Is the ls command a 32 bit
executable then?
Could this be related to the inode overflow in 32 bit
On Mon, Oct 20, 2014 at 01:22:22PM +0100, Filipe Manana wrote:
On 10/20/2014 12:13 AM, Greg KH wrote:
On Sun, Oct 19, 2014 at 09:55:11PM +0200, Greg KH wrote:
On Sun, Oct 19, 2014 at 06:01:16AM -0400, Chris Mason wrote:
Hi everyone,
I've pulled out some of the btrfs commits from the
20 matches
Mail list logo
