On 06/08/2017 07:07 PM, Shaohua Li wrote:
Neil fixed a bug in this side recently, which is pretty similar like the
reported, I'll push the patch to upstream soon. Could you please try my
for-next tree, and check if you still have the issue?
Thanks,
Shaohua
Kernel with the patch applied runs
On 06/08/2017 10:29 AM, Marian Csontos wrote:
Mike, Heinz, help please!
RC4 and still present:
[ 248.815709] CPU: 0 PID: 21 Comm: rcuos/1 Not tainted
4.12.0-0.rc4.git2.1.fc27.x86_64 #1
FYI from changelog: Linux v4.12-rc4-122-gb29794e
Commit b29794e from June 6th which is HEAD of master as
? And if so is it a
known one?
I have not found any reference anywhere except this dm-devel thread.
Is this a problem in LVM RAID only?
Where to forward this? LKML? Fedora Bugzilla?
Is there anything else I should provide?
-- Martian
On 05/18/2017 10:33 AM, Marian Csontos wrote:
When running `lvm
When running `lvm lvcreate --type raid5 --size 4194304B --name meta_r5
LVMTEST12279nqymhamb_vg --yes` there's a warning followed by the bug.
Also at [ 192.140142] it looks like there is an uninitialized variable
somewhere.
env: rawhide, kvm, 2 (V)CPUs
lvm2: upstream
kernel: 4.12.0-0.rc1.git1
Running rawhide in KVM,
kernel:
4.12.0-0.rc1.git1.1.fc27.x86_64
- latest 4.12 build in rawhide
cryptsetup commit:
d9a528922b5d1a15c72936ea2e5e87ce2d31bc3d
- HEAD of wip-luks2 branch as of 2017-05-16
...
[ 1057.722305] buffer_io_error: 146 callbacks suppressed
[ 1057.723514] Buffer I/O error o
On 02/03/2017 05:31 PM, Muneendra Kumar M wrote:
550 5.1.8 : Sender address rejected:
Domain not
found (in reply to RCPT TO command)
Hi Muneendra, you need to setup From header to send the email from an
address with a recognized domain.
There is no localdomain domain as th
On 07/28/2016 03:33 AM, james harvey wrote:
On Wed, Jul 27, 2016 at 2:49 PM, Marian Csontos wrote:
On 07/23/2016 01:14 AM, james harvey wrote:
If I understand what's going on here, I think device-mapper is trying
to work with two volumes that don't involve LVM, causing the error
On 07/23/2016 01:14 AM, james harvey wrote:
If I understand what's going on here, I think device-mapper is trying
to work with two volumes that don't involve LVM, causing the errors.
If I understand correctly, these volumes DO involve LVM.
It is not LV on top of your BTRFS volumes, but your BT
