Thanks for comments, more below..
On 04/30/2016 12:42 AM, David Sterba wrote:
On Thu, Apr 28, 2016 at 11:06:19AM +0800, Anand Jain wrote:
When RAID1 is degraded, newer chunks should be degraded-RAID1
chunks instead of single chunks.
The bug is because the devs_min for raid1 was wrong it shoul
Anand Jain posted on Mon, 02 May 2016 12:12:31 +0800 as excerpted:
> On 04/30/2016 12:37 AM, David Sterba wrote:
>> On Thu, Apr 28, 2016 at 11:06:18AM +0800, Anand Jain wrote:
>>> From the comments that commit[1] deleted
>>>
>>> - /*
>>> - * we add in the count of missing devices because we want
On 04/30/2016 12:37 AM, David Sterba wrote:
On Thu, Apr 28, 2016 at 11:06:18AM +0800, Anand Jain wrote:
From the comments that commit[1] deleted
- /*
- * we add in the count of missing devices because we want
- * to make sure that any RAID levels on a degraded FS
- * continue to be honored.
Thanks! for report.
Sequense was:
1) create FS (RAID5), mount, write 40 MB file, sync
2) detach drive
3) start replace detached (but still not closed) drive by another
4) touch mount point, call 'btrfs fi sync' (I use udev script to initiate write
immediately after drive removal)
4) -> oops.
On 1 May 2016 at 03:00, Kai Krakow wrote:
> Hello!
>
> I'm not sure what triggeres this, neither if it is btrfs specific. The
> filesystems have been recreated from scratch. Mainly during my rsync
> backup (from btrfs to btrfs), but not necessarily limited to rsync
> usage, my system experiences u
Jakob Schürz posted on Sun, 01 May 2016 15:38:22 +0200 as excerpted:
> What does this mean???
>
> Mai 01 15:36:42 aldebaran kernel: [ cut here ]
> Mai 01 15:36:42 aldebaran kernel: WARNING: CPU: 3 PID: 8937 at
> /build/linux-aGlcVo/linux-4.6~rc3/fs/btrfs/inode.c:9261
> btr
Kai Krakow posted on Sun, 01 May 2016 18:54:18 +0200 as excerpted:
> I didn't now about smart-live-rebuild. Interesting. ;-)
Yeah. I didn't know about it until a few years ago, either, including
when I first setup kde4-live, tho at that point I was doing the stable-
branch live, not master live
Kai Krakow posted on Sun, 01 May 2016 18:54:18 +0200 as excerpted:
> It affects all file systems. The "btrfs fi sync" is used to finish my
> rsync backup and ensure everything is written before I'm trying to
> unmount it or the system goes back to sleep.
>
> "df" and friends also freeze on tmp (r
Kai Krakow posted on Sun, 01 May 2016 18:54:18 +0200 as excerpted:
>> > I created a backtrace in dmesg using sysrq+w. Here's the log:
>> > (https://gist.github.com/kakra/8e6a2b7ac4047fa9e345648664f5667b)
>>
>> FWIW, that link give me the github "this is not the web page you are
>> looking for"
On 04/25/2016 11:09 PM, David Sterba wrote:
On Mon, Apr 18, 2016 at 04:51:23PM +0800, Anand Jain wrote:
When the replace target fails, the target device will be taken
out of fs device list, scratch + update_dev_time and freed. However
we could do the scratch + update_dev_time and free part af
Mike Fleetwood posted on Sun, 01 May 2016 14:54:44 +0100 as excerpted:
> On 1 May 2016 at 13:47, Duncan <1i5t5.dun...@cox.net> wrote:
>> Direct from that section of my /etc/sysctl.conf:
>>
>>
>> # Virtual-machine: swa
On 03/16/2016 09:10 PM, David Sterba wrote:
On Thu, Mar 10, 2016 at 12:22:15PM +0800, Anand Jain wrote:
This patch will log return value of add/del_qgroup_relation() and pass the
err code of btrfs_run_qgroups to the btrfs_std_error().
Signed-off-by: Anand Jain
---
v2: fix the forgotten git c
On 04/25/2016 11:15 PM, David Sterba wrote:
On Mon, Apr 18, 2016 at 07:25:52PM +0800, Anand Jain wrote:
Creates helper fucntion as needed by the device delete
and replace operations. Also now it checks if the next
device being assigned is an active device.
Signed-off-by: Anand Jain
--- a/fs/
Creates helper fucntion as needed by the device delete
and replace operations. Also now it checks if the next
device being assigned is an active device.
Signed-off-by: Anand Jain
---
v2: added comments, and BUG_ON if we can't find next_device.
fs/btrfs/dev-replace.c | 8 +++
fs/btrfs/volu
On 04/26/2016 12:23 AM, David Sterba wrote:
On Thu, Mar 24, 2016 at 06:48:13PM +0800, Anand Jain wrote:
Sysfs create context should come in the last, so that we
don't have to undo sysfs operation for the reason that any
other operation has failed.
Moving the sysfs call will make a visible ch
Am Sun, 1 May 2016 12:47:00 + (UTC)
schrieb Duncan <1i5t5.dun...@cox.net>:
> Kai Krakow posted on Sun, 01 May 2016 09:00:46 +0200 as excerpted:
>
> > I'm not sure what triggeres this, neither if it is btrfs specific.
> > The filesystems have been recreated from scratch. Mainly during my
> > r
He Guys!
I think i found a bug in:
uname -a
Linux NAS 4.6.0-rc3-amd64 #1 SMP Debian 4.6~rc3-1~exp1 (2016-04-14)
x86_64 GNU/Linux
The fliesystem has some corrupt sectors caused by an faulty drive.
While adding a new drive, removing the damaged failed, I had some
success with the replace co
On 1 May 2016 at 13:47, Duncan <1i5t5.dun...@cox.net> wrote:
> Direct from that section of my /etc/sysctl.conf:
>
>
> # Virtual-machine: swap, write-cache
Hi Duncan,
You mean virtual memory.
Quoting from the kernel
What does this mean???
Mai 01 15:36:42 aldebaran kernel: [ cut here ]
Mai 01 15:36:42 aldebaran kernel: WARNING: CPU: 3 PID: 8937 at
/build/linux-aGlcVo/linux-4.6~rc3/fs/btrfs/inode.c:9261
btrfs_destroy_inode+0x234/0x2a0 [btrfs]
Mai 01 15:36:42 aldebaran kernel: Modules lin
Kai Krakow posted on Sun, 01 May 2016 09:00:46 +0200 as excerpted:
> I'm not sure what triggeres this, neither if it is btrfs specific. The
> filesystems have been recreated from scratch. Mainly during my rsync
> backup (from btrfs to btrfs), but not necessarily limited to rsync
> usage, my system
Hello!
I'm not sure what triggeres this, neither if it is btrfs specific. The
filesystems have been recreated from scratch. Mainly during my rsync
backup (from btrfs to btrfs), but not necessarily limited to rsync
usage, my system experiences uninterruptable freezes of commands like
"df", "du", "b
Hello!
I'm not sure what triggeres this, neither if it is btrfs specific. The
filesystems have been recreated from scratch. Mainly during my rsync
backup (from btrfs to btrfs), but not necessarily limited to rsync
usage, my system experiences uninterruptable freezes of commands like
"df", "du", "b
22 matches
Mail list logo
