Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: DRBD: Users

"local disk flush failed with status -5" on LVM

 

 

DRBD users RSS feed   Index | Next | Previous | View Threaded


wd at denx

May 3, 2008, 5:19 PM

Post #1 of 13 (5167 views)
Permalink
"local disk flush failed with status -5" on LVM

Hi,

I'm trying to run DRBD on top of a LV, and get flooded with above
error messages. I know this has been discussed before, see threads
starting at
http://lists.linbit.com/pipermail/drbd-user/2008-February/008665.html
and
http://lists.linbit.com/pipermail/drbd-user/2008-February/008519.html

When this was discussed in February, it sounded (at least to me) as is
a fix was on the way, see
http://lists.linbit.com/pipermail/drbd-user/2008-February/008692.html

However, even top of tree from the git repo still shows the same
behaviour.

Am I missing something, or is this usage mode so exotic that nobody
cares?

Thanks in advance.

Best regards,

Wolfgang Denk

--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd [at] denx
Don't panic.
_______________________________________________
drbd-user mailing list
drbd-user [at] lists
http://lists.linbit.com/mailman/listinfo/drbd-user


philipp.reisner at linbit

May 7, 2008, 12:58 AM

Post #2 of 13 (5074 views)
Permalink
Re: "local disk flush failed with status -5" on LVM [In reply to]

Am Sonntag, 4. Mai 2008 02:19:12 schrieb Wolfgang Denk:
> Hi,
>
> I'm trying to run DRBD on top of a LV, and get flooded with above
> error messages. I know this has been discussed before, see threads
> starting at
> http://lists.linbit.com/pipermail/drbd-user/2008-February/008665.html
> and
> http://lists.linbit.com/pipermail/drbd-user/2008-February/008519.html
>
> When this was discussed in February, it sounded (at least to me) as is
> a fix was on the way, see
> http://lists.linbit.com/pipermail/drbd-user/2008-February/008692.html
>
> However, even top of tree from the git repo still shows the same
> behaviour.
>
> Am I missing something, or is this usage mode so exotic that nobody
> cares?
>

Hi Wolfgang,

That is actually a kernel bug, I think in 2.6.24. Was fixed later, do not
know by heart with which "sucker" release. I guess it is fixed in 2.6.25.

Starting with 8.0.12 we offer a workaround for this in DRBD (and 8.2.6
when I finally find the time to finish it):

Add no-disk-flushes and no-md-flushes to your disk config.

-phil
--
: Dipl-Ing Philipp Reisner Tel +43-1-8178292-50 :
: LINBIT Information Technologies GmbH Fax +43-1-8178292-82 :
: Vivenotgasse 48, 1120 Vienna, Austria http://www.linbit.com :
_______________________________________________
drbd-user mailing list
drbd-user [at] lists
http://lists.linbit.com/mailman/listinfo/drbd-user


hanselzen at gmail

May 7, 2008, 3:11 AM

Post #3 of 13 (5071 views)
Permalink
Re: "local disk flush failed with status -5" on LVM [In reply to]

Yes, this is kernel bug. I also have the same problem with you. Your
only choice:
1. Patch your kernel to 2.6.25
2. Don't use DRBD on top LV. ( I choose this way ).

On Wed, May 7, 2008 at 3:58 PM, Philipp Reisner
<philipp.reisner [at] linbit> wrote:
> Am Sonntag, 4. Mai 2008 02:19:12 schrieb Wolfgang Denk:
>
> > Hi,
> >
> > I'm trying to run DRBD on top of a LV, and get flooded with above
> > error messages. I know this has been discussed before, see threads
> > starting at
> > http://lists.linbit.com/pipermail/drbd-user/2008-February/008665.html
> > and
> > http://lists.linbit.com/pipermail/drbd-user/2008-February/008519.html
> >
> > When this was discussed in February, it sounded (at least to me) as is
> > a fix was on the way, see
> > http://lists.linbit.com/pipermail/drbd-user/2008-February/008692.html
> >
> > However, even top of tree from the git repo still shows the same
> > behaviour.
> >
> > Am I missing something, or is this usage mode so exotic that nobody
> > cares?
> >
>
> Hi Wolfgang,
>
> That is actually a kernel bug, I think in 2.6.24. Was fixed later, do not
> know by heart with which "sucker" release. I guess it is fixed in 2.6.25.
>
> Starting with 8.0.12 we offer a workaround for this in DRBD (and 8.2.6
> when I finally find the time to finish it):
>
> Add no-disk-flushes and no-md-flushes to your disk config.
>
> -phil
> --
> : Dipl-Ing Philipp Reisner Tel +43-1-8178292-50 :
> : LINBIT Information Technologies GmbH Fax +43-1-8178292-82 :
> : Vivenotgasse 48, 1120 Vienna, Austria http://www.linbit.com :
>
>
> _______________________________________________
> drbd-user mailing list
> drbd-user [at] lists
> http://lists.linbit.com/mailman/listinfo/drbd-user
>



--
Best Regards,
David Hansel
_______________________________________________
drbd-user mailing list
drbd-user [at] lists
http://lists.linbit.com/mailman/listinfo/drbd-user


iustin at google

May 10, 2008, 3:28 AM

Post #4 of 13 (5030 views)
Permalink
Re: "local disk flush failed with status -5" on LVM [In reply to]

Philipp Reisner wrote:
> Am Sonntag, 4. Mai 2008 02:19:12 schrieb Wolfgang Denk:
> > Hi,
> >
> > I'm trying to run DRBD on top of a LV, and get flooded with above
> > error messages. I know this has been discussed before, see threads
> > starting at
> > http://lists.linbit.com/pipermail/drbd-user/2008-February/008665.html
> > and
> > http://lists.linbit.com/pipermail/drbd-user/2008-February/008519.html
> >
> > When this was discussed in February, it sounded (at least to me) as is
> > a fix was on the way, see
> > http://lists.linbit.com/pipermail/drbd-user/2008-February/008692.html
> >
> > However, even top of tree from the git repo still shows the same
> > behaviour.
> >
> > Am I missing something, or is this usage mode so exotic that nobody
> > cares?
> >
>
> Hi Wolfgang,
>
> That is actually a kernel bug, I think in 2.6.24. Was fixed later, do not
> know by heart with which "sucker" release. I guess it is fixed in 2.6.25.
>
> Starting with 8.0.12 we offer a workaround for this in DRBD (and 8.2.6
> when I finally find the time to finish it):
>
> Add no-disk-flushes and no-md-flushes to your disk config.

Because this happens not only with LVM, but with any I/O subsystem that
returns wrong error codes from flushes (e.g. broken scsi drivers or
controller, I think), would it be a sane thing to disable barriers
automatically if there after a certain number of errors?

(Looking at the barrier flush code I see that only the drbd_receiver.c
has code for auto-disabling in case of EOPNOTSUPP, but drbd_actlog and
drbd_bitmap.c don't; maybe these too should have this).

The reason I propose this is because with many deployments on different
machines it would be better to let it always enabled at startup and
allow it to autodisable if it see EOPNOTSUPP or too many other errors.
And people can't always track latest upstream kernel...

thanks,
iustin
_______________________________________________
drbd-user mailing list
drbd-user [at] lists
http://lists.linbit.com/mailman/listinfo/drbd-user


sjourdan at reservit

May 12, 2008, 8:33 AM

Post #5 of 13 (5031 views)
Permalink
"local disk flush failed with status -5" on LVM [In reply to]

Hi,

I'm currently using DRBD over LVM and getting the same error message
than http://lists.linbit.com/pipermail/drbd-user/2008-May/009287.html

Upgrading the kernel to 2.6.25 is not an option for now (running
Ubuntu/2.6.24)
But even using the latest sources from git or v8.0.12 and using the 2
new options to disable flushes, I get the "disk flush" failures .

As per the last message posted on this topic, is this kernel bug fixed
by the workaround you provided ? Or is it, but not in the case of a
DRBD-over-LVM setup (and then, only upgrading the kernel would help) ?

Thanks for your help!

Cheers,
Stef

--
Stephane Jourdan
sjourdan [at] reservit

_______________________________________________
drbd-user mailing list
drbd-user [at] lists
http://lists.linbit.com/mailman/listinfo/drbd-user


lars.ellenberg at linbit

May 13, 2008, 1:50 AM

Post #6 of 13 (5024 views)
Permalink
Re: "local disk flush failed with status -5" on LVM [In reply to]

On Sat, May 10, 2008 at 12:28:00PM +0200, Iustin Pop wrote:
> Philipp Reisner wrote:
> > Am Sonntag, 4. Mai 2008 02:19:12 schrieb Wolfgang Denk:
> > > Hi,
> > >
> > > I'm trying to run DRBD on top of a LV, and get flooded with above
> > > error messages. I know this has been discussed before, see threads
> > > starting at
> > > http://lists.linbit.com/pipermail/drbd-user/2008-February/008665.html
> > > and
> > > http://lists.linbit.com/pipermail/drbd-user/2008-February/008519.html
> > >
> > > When this was discussed in February, it sounded (at least to me) as is
> > > a fix was on the way, see
> > > http://lists.linbit.com/pipermail/drbd-user/2008-February/008692.html
> > >
> > > However, even top of tree from the git repo still shows the same
> > > behaviour.
> > >
> > > Am I missing something, or is this usage mode so exotic that nobody
> > > cares?
> > >
> >
> > Hi Wolfgang,
> >
> > That is actually a kernel bug, I think in 2.6.24. Was fixed later, do not
> > know by heart with which "sucker" release. I guess it is fixed in 2.6.25.
> >
> > Starting with 8.0.12 we offer a workaround for this in DRBD (and 8.2.6
> > when I finally find the time to finish it):
> >
> > Add no-disk-flushes and no-md-flushes to your disk config.
>
> Because this happens not only with LVM, but with any I/O subsystem that
> returns wrong error codes from flushes (e.g. broken scsi drivers or
> controller, I think), would it be a sane thing to disable barriers
> automatically if there after a certain number of errors?
>
> (Looking at the barrier flush code I see that only the drbd_receiver.c
> has code for auto-disabling in case of EOPNOTSUPP, but drbd_actlog and
> drbd_bitmap.c don't; maybe these too should have this).

hm?
I think we do have a retry-and-disable-barriers in those places too.

> The reason I propose this is because with many deployments on different
> machines it would be better to let it always enabled at startup and
> allow it to autodisable if it see EOPNOTSUPP

that is the way we do it.

> or too many other errors.

and that is what we don't.

> And people can't always track latest upstream kernel...

if they are stuck with a kernel where DRBD spits out too much
noise due to barrier requests throwing IO errors,
then they have to disable use of barriers in the drbd config.

--
: Lars Ellenberg http://www.linbit.com :
: DRBD/HA support and consulting sales at linbit.com :
: LINBIT Information Technologies GmbH Tel +43-1-8178292-0 :
: Vivenotgasse 48, A-1120 Vienna/Europe Fax +43-1-8178292-82 :
__
please don't Cc me, but send to list -- I'm subscribed
_______________________________________________
drbd-user mailing list
drbd-user [at] lists
http://lists.linbit.com/mailman/listinfo/drbd-user


iustin at google

May 13, 2008, 1:58 AM

Post #7 of 13 (5005 views)
Permalink
Re: "local disk flush failed with status -5" on LVM [In reply to]

On Tue, May 13, 2008 at 10:50:22AM +0200, Lars Ellenberg wrote:
> On Sat, May 10, 2008 at 12:28:00PM +0200, Iustin Pop wrote:
> > Philipp Reisner wrote:
> > > Am Sonntag, 4. Mai 2008 02:19:12 schrieb Wolfgang Denk:
> > > > Hi,
> > > >
> > > > I'm trying to run DRBD on top of a LV, and get flooded with above
> > > > error messages. I know this has been discussed before, see threads
> > > > starting at
> > > > http://lists.linbit.com/pipermail/drbd-user/2008-February/008665.html
> > > > and
> > > > http://lists.linbit.com/pipermail/drbd-user/2008-February/008519.html
> > > >
> > > > When this was discussed in February, it sounded (at least to me) as is
> > > > a fix was on the way, see
> > > > http://lists.linbit.com/pipermail/drbd-user/2008-February/008692.html
> > > >
> > > > However, even top of tree from the git repo still shows the same
> > > > behaviour.
> > > >
> > > > Am I missing something, or is this usage mode so exotic that nobody
> > > > cares?
> > > >
> > >
> > > Hi Wolfgang,
> > >
> > > That is actually a kernel bug, I think in 2.6.24. Was fixed later, do not
> > > know by heart with which "sucker" release. I guess it is fixed in 2.6.25.
> > >
> > > Starting with 8.0.12 we offer a workaround for this in DRBD (and 8.2.6
> > > when I finally find the time to finish it):
> > >
> > > Add no-disk-flushes and no-md-flushes to your disk config.
> >
> > Because this happens not only with LVM, but with any I/O subsystem that
> > returns wrong error codes from flushes (e.g. broken scsi drivers or
> > controller, I think), would it be a sane thing to disable barriers
> > automatically if there after a certain number of errors?
> >
> > (Looking at the barrier flush code I see that only the drbd_receiver.c
> > has code for auto-disabling in case of EOPNOTSUPP, but drbd_actlog and
> > drbd_bitmap.c don't; maybe these too should have this).
>
> hm?
> I think we do have a retry-and-disable-barriers in those places too.

I must be wrong then; I'm looking at the drbd 8.0 git tree, and I see in
drbd_bitmap.c:

if (rw == WRITE) {
/* swap back endianness */
bm_lel_to_cpu(b);
/* flush bitmap to stable storage */
if (!test_bit(MD_NO_BARRIER,&mdev->flags))
blkdev_issue_flush(mdev->bc->md_bdev, NULL);

(around line 745). This just issues the flush, and no retry/disable in place
(it uses the same blkdev_issue_flush as drbd_receiver.c, and there's no check
of the return value).

What am I missing here? Wrong git tree?

> > The reason I propose this is because with many deployments on different
> > machines it would be better to let it always enabled at startup and
> > allow it to autodisable if it see EOPNOTSUPP
>
> that is the way we do it.
>
> > or too many other errors.
>
> and that is what we don't.

Would it make sense to do it if no blkdev_issue_flush is ever successfull?

> > And people can't always track latest upstream kernel...
>
> if they are stuck with a kernel where DRBD spits out too much
> noise due to barrier requests throwing IO errors,
> then they have to disable use of barriers in the drbd config.

Ok, let me explain some more. If you have deployments on the order of hundreds
of machines, with various types of controllers, it would be easier to let the
config always have barriers enabled and rely on auto-disable if *no single
flush is ever successfull*.

What do you think?

regards,
iustin
_______________________________________________
drbd-user mailing list
drbd-user [at] lists
http://lists.linbit.com/mailman/listinfo/drbd-user


lars.ellenberg at linbit

May 13, 2008, 7:11 AM

Post #8 of 13 (5036 views)
Permalink
Re: "local disk flush failed with status -5" on LVM [In reply to]

On Tue, May 13, 2008 at 10:58:29AM +0200, Iustin Pop wrote:
> On Tue, May 13, 2008 at 10:50:22AM +0200, Lars Ellenberg wrote:
> > On Sat, May 10, 2008 at 12:28:00PM +0200, Iustin Pop wrote:
> > > Philipp Reisner wrote:
> > > > Am Sonntag, 4. Mai 2008 02:19:12 schrieb Wolfgang Denk:
> > > > > Hi,
> > > > >
> > > > > I'm trying to run DRBD on top of a LV, and get flooded with above
> > > > > error messages. I know this has been discussed before, see threads
> > > > > starting at
> > > > > http://lists.linbit.com/pipermail/drbd-user/2008-February/008665.html
> > > > > and
> > > > > http://lists.linbit.com/pipermail/drbd-user/2008-February/008519.html
> > > > >
> > > > > When this was discussed in February, it sounded (at least to me) as is
> > > > > a fix was on the way, see
> > > > > http://lists.linbit.com/pipermail/drbd-user/2008-February/008692.html
> > > > >
> > > > > However, even top of tree from the git repo still shows the same
> > > > > behaviour.
> > > > >
> > > > > Am I missing something, or is this usage mode so exotic that nobody
> > > > > cares?
> > > > >
> > > >
> > > > Hi Wolfgang,
> > > >
> > > > That is actually a kernel bug, I think in 2.6.24. Was fixed later, do not
> > > > know by heart with which "sucker" release. I guess it is fixed in 2.6.25.
> > > >
> > > > Starting with 8.0.12 we offer a workaround for this in DRBD (and 8.2.6
> > > > when I finally find the time to finish it):
> > > >
> > > > Add no-disk-flushes and no-md-flushes to your disk config.
> > >
> > > Because this happens not only with LVM, but with any I/O subsystem that
> > > returns wrong error codes from flushes (e.g. broken scsi drivers or
> > > controller, I think), would it be a sane thing to disable barriers
> > > automatically if there after a certain number of errors?
> > >
> > > (Looking at the barrier flush code I see that only the drbd_receiver.c
> > > has code for auto-disabling in case of EOPNOTSUPP, but drbd_actlog and
> > > drbd_bitmap.c don't; maybe these too should have this).
> >
> > hm?
> > I think we do have a retry-and-disable-barriers in those places too.
>
> I must be wrong then; I'm looking at the drbd 8.0 git tree, and I see in
> drbd_bitmap.c:
>
> if (rw == WRITE) {
> /* swap back endianness */
> bm_lel_to_cpu(b);
> /* flush bitmap to stable storage */
> if (!test_bit(MD_NO_BARRIER,&mdev->flags))
> blkdev_issue_flush(mdev->bc->md_bdev, NULL);
>
> (around line 745). This just issues the flush, and no retry/disable in place
> (it uses the same blkdev_issue_flush as drbd_receiver.c, and there's no check
> of the return value).
>
> What am I missing here? Wrong git tree?

grep for set_bit MD_NO_BARRIER

> > > The reason I propose this is because with many deployments on different
> > > machines it would be better to let it always enabled at startup and
> > > allow it to autodisable if it see EOPNOTSUPP
> >
> > that is the way we do it.
> >
> > > or too many other errors.
> >
> > and that is what we don't.
>
> Would it make sense to do it if no blkdev_issue_flush is ever successfull?
>
> > > And people can't always track latest upstream kernel...
> >
> > if they are stuck with a kernel where DRBD spits out too much
> > noise due to barrier requests throwing IO errors,
> > then they have to disable use of barriers in the drbd config.
>
> Ok, let me explain some more. If you have deployments on the order of hundreds
> of machines, with various types of controllers, it would be easier to let the
> config always have barriers enabled and rely on auto-disable if *no single
> flush is ever successfull*.

buy a support contract,
have a script parse log files and auto-adjust them,
or send a patch.

--
: Lars Ellenberg http://www.linbit.com :
: DRBD/HA support and consulting sales at linbit.com :
: LINBIT Information Technologies GmbH Tel +43-1-8178292-0 :
: Vivenotgasse 48, A-1120 Vienna/Europe Fax +43-1-8178292-82 :
__
please don't Cc me, but send to list -- I'm subscribed
_______________________________________________
drbd-user mailing list
drbd-user [at] lists
http://lists.linbit.com/mailman/listinfo/drbd-user


iustin at google

May 13, 2008, 7:15 AM

Post #9 of 13 (5032 views)
Permalink
Re: "local disk flush failed with status -5" on LVM [In reply to]

On Tue, May 13, 2008 at 04:11:11PM +0200, Lars Ellenberg wrote:
> > Ok, let me explain some more. If you have deployments on the order of hundreds
> > of machines, with various types of controllers, it would be easier to let the
> > config always have barriers enabled and rely on auto-disable if *no single
> > flush is ever successfull*.
>
> buy a support contract,
> have a script parse log files and auto-adjust them,
> or send a patch.

Don't know if I'm able to write a nice patch, but (as soon as I'm back
from a vacation) I'll try to put something together.

Thanks!

iustin
_______________________________________________
drbd-user mailing list
drbd-user [at] lists
http://lists.linbit.com/mailman/listinfo/drbd-user


philipp.reisner at linbit

May 14, 2008, 3:39 AM

Post #10 of 13 (5011 views)
Permalink
Re: "local disk flush failed with status -5" on LVM [In reply to]

Am Montag, 12. Mai 2008 17:33:19 schrieb Stephane Jourdan:
> Hi,
>
> I'm currently using DRBD over LVM and getting the same error message
> than http://lists.linbit.com/pipermail/drbd-user/2008-May/009287.html
>
> Upgrading the kernel to 2.6.25 is not an option for now (running
> Ubuntu/2.6.24)
> But even using the latest sources from git or v8.0.12 and using the 2
> new options to disable flushes, I get the "disk flush" failures .
>
> As per the last message posted on this topic, is this kernel bug fixed
> by the workaround you provided ? Or is it, but not in the case of a
> DRBD-over-LVM setup (and then, only upgrading the kernel would help) ?
>
> Thanks for your help!
>

Hi Stef,

Can you please post the output of drbdsetup /dev/drbdX show,
and and excerpt of the kernel logs with the disk flush failures ?

Thanks!
-phil
--
: Dipl-Ing Philipp Reisner Tel +43-1-8178292-50 :
: LINBIT Information Technologies GmbH Fax +43-1-8178292-82 :
: Vivenotgasse 48, 1120 Vienna, Austria http://www.linbit.com :
_______________________________________________
drbd-user mailing list
drbd-user [at] lists
http://lists.linbit.com/mailman/listinfo/drbd-user


sjourdan at reservit

May 14, 2008, 9:00 AM

Post #11 of 13 (5004 views)
Permalink
Re: "local disk flush failed with status -5" on LVM [In reply to]

Hi Philipp,

So here is the DRBD setup :

~# drbdsetup /dev/drbd1 show
disk {
size 0s _is_default; # bytes
on-io-error pass_on _is_default;
fencing dont-care _is_default;
}
net {
timeout 60 _is_default; # 1/10 seconds
max-epoch-size 2048 _is_default;
max-buffers 2048 _is_default;
unplug-watermark 128 _is_default;
connect-int 10 _is_default; # seconds
ping-int 10 _is_default; # seconds
sndbuf-size 131070 _is_default; # bytes
ko-count 0 _is_default;
allow-two-primaries;
after-sb-0pri discard-zero-changes;
after-sb-1pri discard-secondary;
after-sb-2pri disconnect _is_default;
rr-conflict disconnect _is_default;
ping-timeout 5 _is_default; # 1/10 seconds
}
syncer {
rate 700000k; # bytes/second
after -1 _is_default;
al-extents 127 _is_default;
}
protocol C;
_this_host {
device "/dev/drbd1";
disk "/dev/VG-FULL/dbslash";
meta-disk internal;
address 10.2.10.2:7790;
}
_remote_host {
address 10.2.10.1:7790;
}

and here are some generic /var/log/syslog outputs:
May 14 17:51:38 vlab02 kernel: [110343.557916] drbd1: local disk flush
failed with status -5
May 14 17:51:38 vlab02 kernel: [110343.561781] drbd1: local disk flush
failed with status -5
May 14 17:51:38 vlab02 kernel: [110343.562510] drbd1: local disk flush
failed with status -5
May 14 17:51:38 vlab02 kernel: [110343.565992] drbd1: local disk flush
failed with status -5
May 14 17:51:38 vlab02 kernel: [110343.566476] drbd1: local disk flush
failed with status -5

Some background information : there is 2 machines, whose hard-disks are
mounted on LVM and as you can see in the DRBD config, and the base
device for DRBD is a logical volume. On this DRBD disk is installed a
Xen virtual machine, it's its rootFS.
Everything is really working great, with great Gigabit speed and sync
functions.

This is the exact same setup on both machines, same hardware, same packages.

The errors shown above arrive simply by ssh'ing into the virtual
machine, or creating files, etc.

By the way, I'm using Ubuntu 8.04 with the Xen kernel, and a v8.0.12 DRBD.

Thank you a lot for your help !

Cheers,
Stef


Philipp Reisner wrote:
> Am Montag, 12. Mai 2008 17:33:19 schrieb Stephane Jourdan:
>
>> Hi,
>>
>> I'm currently using DRBD over LVM and getting the same error message
>> than http://lists.linbit.com/pipermail/drbd-user/2008-May/009287.html
>>
>> Upgrading the kernel to 2.6.25 is not an option for now (running
>> Ubuntu/2.6.24)
>> But even using the latest sources from git or v8.0.12 and using the 2
>> new options to disable flushes, I get the "disk flush" failures .
>>
>> As per the last message posted on this topic, is this kernel bug fixed
>> by the workaround you provided ? Or is it, but not in the case of a
>> DRBD-over-LVM setup (and then, only upgrading the kernel would help) ?
>>
>> Thanks for your help!
>>
>>
>
> Hi Stef,
>
> Can you please post the output of drbdsetup /dev/drbdX show,
> and and excerpt of the kernel logs with the disk flush failures ?
>
> Thanks!
> -phil
>

--
Stephane Jourdan
ReservIT
sjourdan [at] reservit

_______________________________________________
drbd-user mailing list
drbd-user [at] lists
http://lists.linbit.com/mailman/listinfo/drbd-user


philipp.reisner at linbit

May 15, 2008, 12:02 AM

Post #12 of 13 (4993 views)
Permalink
Re: "local disk flush failed with status -5" on LVM [In reply to]

Am Mittwoch, 14. Mai 2008 18:00:15 schrieb Stephane Jourdan:
> Hi Philipp,
>
> So here is the DRBD setup :
>
> ~# drbdsetup /dev/drbd1 show
> disk {
> size 0s _is_default; # bytes
> on-io-error pass_on _is_default;
> fencing dont-care _is_default;
> }
> net {
> timeout 60 _is_default; # 1/10 seconds
> max-epoch-size 2048 _is_default;
> max-buffers 2048 _is_default;
> unplug-watermark 128 _is_default;
> connect-int 10 _is_default; # seconds
> ping-int 10 _is_default; # seconds
> sndbuf-size 131070 _is_default; # bytes
> ko-count 0 _is_default;
> allow-two-primaries;
> after-sb-0pri discard-zero-changes;
> after-sb-1pri discard-secondary;
> after-sb-2pri disconnect _is_default;
> rr-conflict disconnect _is_default;
> ping-timeout 5 _is_default; # 1/10 seconds
> }
> syncer {
> rate 700000k; # bytes/second
> after -1 _is_default;
> al-extents 127 _is_default;
> }
> protocol C;
> _this_host {
> device "/dev/drbd1";
> disk "/dev/VG-FULL/dbslash";
> meta-disk internal;
> address 10.2.10.2:7790;
> }
> _remote_host {
> address 10.2.10.1:7790;
> }
>
> and here are some generic /var/log/syslog outputs:
> May 14 17:51:38 vlab02 kernel: [110343.557916] drbd1: local disk flush
> failed with status -5
> May 14 17:51:38 vlab02 kernel: [110343.561781] drbd1: local disk flush
> failed with status -5
> May 14 17:51:38 vlab02 kernel: [110343.562510] drbd1: local disk flush
> failed with status -5
> May 14 17:51:38 vlab02 kernel: [110343.565992] drbd1: local disk flush
> failed with status -5
> May 14 17:51:38 vlab02 kernel: [110343.566476] drbd1: local disk flush
> failed with status -5
>
> Some background information : there is 2 machines, whose hard-disks are
> mounted on LVM and as you can see in the DRBD config, and the base
> device for DRBD is a logical volume. On this DRBD disk is installed a
> Xen virtual machine, it's its rootFS.
> Everything is really working great, with great Gigabit speed and sync
> functions.
>
> This is the exact same setup on both machines, same hardware, same
> packages.
>
> The errors shown above arrive simply by ssh'ing into the virtual
> machine, or creating files, etc.
>
> By the way, I'm using Ubuntu 8.04 with the Xen kernel, and a v8.0.12 DRBD.
>
> Thank you a lot for your help !
>
> Cheers,
> Stef

Quoted from you initial mail:
[...]
> >> Upgrading the kernel to 2.6.25 is not an option for now (running
> >> Ubuntu/2.6.24)
> >> But even using the latest sources from git or v8.0.12 and using the 2
> >> new options to disable flushes, I get the "disk flush" failures .
> >>
[...]
> > Can you please post the output of drbdsetup /dev/drbdX show,
> > and and excerpt of the kernel logs with the disk flush failures ?
[...]
> ~# drbdsetup /dev/drbd1 show
> disk {
> size 0s _is_default; # bytes
> on-io-error pass_on _is_default;
> fencing dont-care _is_default;
> }

I expected it like this:

disk {
size 0s _is_default; # bytes
on-io-error pass_on _is_default;
fencing dont-care _is_default;
no-disk-flushes ;
no-md-flushes ;
}

Probably you added the two no-flushes options to the config, but forgot
to make sure that the changes are also propagated to the running config.

Simply do an down / up, or an adjust.

-Phil
--
: Dipl-Ing Philipp Reisner Tel +43-1-8178292-50 :
: LINBIT Information Technologies GmbH Fax +43-1-8178292-82 :
: Vivenotgasse 48, 1120 Vienna, Austria http://www.linbit.com :
_______________________________________________
drbd-user mailing list
drbd-user [at] lists
http://lists.linbit.com/mailman/listinfo/drbd-user


sjourdan at reservit

May 15, 2008, 2:59 AM

Post #13 of 13 (4983 views)
Permalink
Re: "local disk flush failed with status -5" on LVM [In reply to]

Philipp Reisner wrote:
> [...]
>
>> ~# drbdsetup /dev/drbd1 show
>> disk {
>> size 0s _is_default; # bytes
>> on-io-error pass_on _is_default;
>> fencing dont-care _is_default;
>> }
>>
>
> I expected it like this:
>
> disk {
> size 0s _is_default; # bytes
> on-io-error pass_on _is_default;
> fencing dont-care _is_default;
> no-disk-flushes ;
> no-md-flushes ;
> }
>
> Probably you added the two no-flushes options to the config, but forgot
> to make sure that the changes are also propagated to the running config.
>
> Simply do an down / up, or an adjust.
>
> -Phil
>
Okay I found the problem, stoopid me. By default, version 8.0.11
(shipped by Ubuntu) was still running and not v8.0.12. A quick depmod
later and 8.0.12 is up & running ... I should have checked before that
8.0.12 was actually running or not after compilation.

And now everything's ok, obviously.

Thanks a lot for your help!

Cheers,
Stef

--
Stephane Jourdan
ReservIT
sjourdan [at] reservit

_______________________________________________
drbd-user mailing list
drbd-user [at] lists
http://lists.linbit.com/mailman/listinfo/drbd-user

DRBD users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.