On Sun, Jul 12, 2015 at 7:23 PM, René Pfeiffer l...@luchs.at wrote:
Hello!
I also hit the Btrfs read-only after btrfs-convert bug when converting my
Ext4 root filesystem with btrfs-convert. I used the btrfs tools v4.0 and
Linux kernel 4.1.1.
As a workaround I mounted the converted Btrfs
This patch introduces new option devid for the command
btrfs device delete device_path|devid[..] mnt
In a user reported issue on a 3-disk-RAID1, one disk failed with its
SB unreadable. Now with this patch user will have a choice to delete
the device using devid.
The other method we could do,
On 07/11/2015 01:28 AM, None None wrote:
I can't apply your patch on btrfs-progs v4.1 nor v4.0
http://www.spinics.net/lists/linux-btrfs/msg43422.html
git apply --check
error: Documentation/btrfs-device.txt: No such file or directory
error: patch failed: cmds-device.c:169
error:
Just a final note -- I'm finally back in person with the CentOS 7 server and so
booted it to the latest kernel-ml from elrepo. It is a 4.1 kernel.
But while still remote with the older 3.10 kernel, I also tried doing
a 'mount -oremount,clear_cache /'
I can't swear it helped, but things did seem
On Sun, Jul 12, 2015 at 2:54 AM, Martin Steigerwald mar...@lichtvoll.de wrote:
Note however: Even without sync BTRFS will defragment the file. It may
just take a while till the new extents are written. So there is no need to
call sync after btrfs fi defrag.
My purpose in calling sync in that
Hello!
I also hit the Btrfs read-only after btrfs-convert bug when converting my
Ext4 root filesystem with btrfs-convert. I used the btrfs tools v4.0 and
Linux kernel 4.1.1.
As a workaround I mounted the converted Btrfs read-only and copied it to a
new Btrfs created by mkfs.btrfs (from the btrfs
On Sat, Jul 11, 2015 at 08:55:23PM -0700, Marc MERLIN wrote:
On Fri, Jul 10, 2015 at 12:46:24PM +0200, Axel Burri wrote:
On 2015-07-09 14:26, Martin Steigerwald wrote:
Well I may try it for one of my BTRFS volumes in addition to the rsync
backup for now. I would like to give all
Am Samstag, 11. Juli 2015, 10:40:29 schrieb erp...@gmail.com:
On Sat, Jul 11, 2015 at 4:12 AM, Martin Steigerwald mar...@lichtvoll.de
wrote:
Always do sync after a btrfs fi defrag and before measuring with
filefrag. The kernel may not have written everything. I have seen this
repeatedly
Hi,
I hope it's not out of place, but I have a few suggestions for the Wiki:
- The presentation NYLUG Presents: Chris Mason on Btrfs (May 14th 2015) at
https://www.youtube.com/watch?v=W3QRWUfBua8 would make a nice addition to the
Articles, presentations, podcasts section.
- The same goes
Greetings,
Looking at the code of should_cow_block(), I see:
if (btrfs_header_generation(buf) == trans-transid
!btrfs_header_flag(buf, BTRFS_HEADER_FLAG_WRITTEN)
...
So if the extent buffer has been written to disk, and now is changed again
in the same transaction, we insist on COW'ing it.
10 matches
Mail list logo