Liuwenyi wrote:
Maybe, you should send this patch to
Andrew Morton a...@linux-foundation.org
Andrea Arcangeli aarca...@redhat.com
Michael S. Tsirkin m...@redhat.com
linux-ker...@vger.kernel.org
linux...@kvack.org
I said in [00] that I sent this patch to Andrew.
What I did not say was it
On Wed, Jan 20, 2010 at 7:28 AM, Aneesh Kumar K. V
aneesh.ku...@linux.vnet.ibm.com wrote:
the below change fixes this for me on btrfs
Thanks a million, now I guess we're waiting for Chris to pull it.
Will it qualify for stable update?
--
This message represents the official view of the voices
On Mon, Jan 18, 2010 at 05:11:53PM -0500, Jim Faulkner wrote:
On Mon, 18 Jan 2010, Chris Mason wrote:
Currently the only compression algorithm we support is gzip, so try
gzipp'ing
your database to get a better comparison. The plan is to eventually support
other compression algorithms,
jim owens wrote:
What I did not say was it was sent on December 9, 2009
to every addess on your list, except for Andrea.
OK, as josef told me, the patch is corrupt and will not apply.
I am sending a new one I just made against btrfs-unstable
to linux-btrfs and will create a new patch for
Hi list
I tried to mount the intact device of a two memer btrfs raid array with one
device missing:
# mount -o degraded /dev/sdb /mnt
this wouldn't work with kernel 2.6.32-2 - caused some sort of memory segfault
# btrfs-vol -r missing /mnt
complained and refused to mount the array degraded
On Mon, Jan 18, 2010 at 08:36:37PM +0100, Carlos R. Mafra wrote:
On Mo 18.Jan'10 at 12:14:43 -0600, Ravi Pinjala wrote:
On 01/18/10 11:17, Carlos R. Mafra wrote:
Hi everyone,
I am using btrfs for my /home partition since I upgraded my slow
laptop hdd for an ssd 3 weeks ago. I am always
On Mon, Jan 18, 2010 at 11:45:40PM +0100, Ronny H. Kavli wrote:
I've been running btrfs on some disks with Ubuntu kernel 2.6.31 for a
while now. Recently I had a bad USB-cable to one of those disks which
left the btrfs filesystem in a somewhat sad state. Fair enough.
What worries me is what
On Mon, Jan 18, 2010 at 11:45:40PM +0100, Ronny H. Kavli wrote:
BTW: Is there any hope of recovery of this filesystem, or is it just a
new mkfs that can help?
I'd expect that we can help at least copy some data off.
-chris
--
To unsubscribe from this list: send the line unsubscribe
Rawhide is getting cranky with posix compliance, and a few
things have stopped building.
getpagesize() is now only available -with- __USE_XOPEN_EXTENDED
or __USE_BSD, and NOT __USE_XOPEN2K.
_GNU_SOURCE must define __USE_XOPEN2K because getpagesize()
has gone away for mkfs. I gave up and used
Well, it fails the way that I'm trying to do it.
kernel:2.6.31.9-174.fc12.x86_64
btrfs-progs: btrfs-progs-0.19-9.fc12.x86_64
On a new filesystem:
$ cd /mnt/btrfs1
$ btrfsctl -S subvol1 .
operation complete
Btrfs Btrfs v0.19
$ btrfsctl -s snapofsubvol1 subvol1
operation complete
Hello,
I get the following error if I edit fstab with vi on a fresh btrfs
filesystem. vi Segfaults at saving the file.
# mkfs.btrfs /dev/sda2
# mount /mnt/
# cd /
# find . -xdev | cpio -vdump /mnt
# vi /mnt/etc/fstab
Segmentation fault
This also happens with a 'cp -a':
# cd /mnt/
# cp
Sander wrote (ao):
I get the following error if I edit fstab with vi on a fresh btrfs
filesystem. vi Segfaults at saving the file.
# mkfs.btrfs /dev/sda2
# mount /mnt/
# cd /
# find . -xdev | cpio -vdump /mnt
# vi /mnt/etc/fstab
Segmentation fault
This also happens with a 'cp -a':
12 matches
Mail list logo