Re: performance issue (was: Re: kernel: BUG: soft lockup - CPU#1 stuck for 60s!)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Rainer Fügenstein <rfu@xxxxxxxxxx> writes:

> Hello Neil,
>
> Sunday, October 25, 2015, 9:08:39 PM, you wrote:
>
>> Depending on kernel version, it will either work or it won't.
> # mdadm --grow /dev/md0 --bitmap=none
> mdadm: failed to remove internal bitmap.
> md: couldn't update array info. -16
>
> so it doesn't work with this kernel. will upgrade ASAP.
>
>> Either way, it won't cause harm.
> famous last words ;-)
>
>> Weekly is a bit more often than I would go for, but why disable it?
> because  a  resync  runs  for a bit more than two days. but running it
> monthly seems to be a good trade-off.
>
>> That isn't a cronjob started resync. That would say "check" rather than
>> 'resync".
>> This looks a lot like a resync after an unclean restart.  But with the
>> bitmap that should go faster...
> you've   got   me  here.  resync  started at 04:22am, the same time as
> cron.weekly.  there  was  a  99-raid-something  script  in cron.weekly
> (before  I  deleted  it).   system  is  up  for some 2 days before the
> resync, so no unclean restart.

Hmmm... is your kernel older than 2.6.19?  If so, that would explain it.
Prior to 2.6.19, 'check' was reported as 'resync'.

>
>> What does "mdadm --examine-bitmap /dev/sdb1" report?
>
> # mdadm --examine-bitmap /dev/sdb1
>         Filename : /dev/sdb1
>            Magic : 6d746962
>          Version : 4
>             UUID : 8d3586a2:6adbc781:ee187e6d:500f9b34
>           Events : 4945261
>   Events Cleared : 4945261
>            State : OK
>        Chunksize : 4 MB
>           Daemon : 5s flush period
>       Write Mode : Normal
>        Sync Size : 2930265344 (2794.52 GiB 3000.59 GB)
>           Bitmap : 715397 bits (chunks), 51 dirty (0.0%)

50% dirty!  That is more than I would expect.  So even if it was a real
resync it would be going quite slowly.  I guess you'll just have to wait
it out.

Maybe you could:
  echo idle > /sys/block/md0/md/sync_action

That will abort a 'check'.  If it restarts automatically, md thinks it
was doing a real resync.  If it doesn't you should be able to remove and
re-add the bitmap.
Then maybe check with --examine-bitmap again.

But definitely update your kernel if you are on 2.6.something.

NeilBrown


>
> hth.
>
> -- 
> Best regards,
>  Rainer                            mailto:rfu@xxxxxxxxxx

Attachment: signature.asc
Description: PGP signature


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux