On Sun, Jan 22, 2012 at 08:52:52PM +0400, Michael Tokarev wrote:
> think of a case when you created
> the array with your clock was set wrong (say, 500
> years in the future) -- it will never be checked
> in this case...
Yep.
> Yes there are easy ways to work
> around this very case - eg, to ve
On 22.01.2012 18:49, Sergey B Kirpichev wrote:
> tag 624273 +patch
> thanks
>
> A simple patch attached.
I don't think that fixing this is a good idea. The
reason is simple: think of a case when you created
the array with your clock was set wrong (say, 500
years in the future) -- it will never b
tag 624273 +patch
thanks
A simple patch attached.
>From 25f0fd586192ec2567344a5beceb16d2f8ef7959 Mon Sep 17 00:00:00 2001
From: Sergey B Kirpichev
Date: Sun, 22 Jan 2012 18:38:30 +0400
Subject: [PATCH] Cancel check for recently created arrays
---
debian/checkarray |7 +++
1 files change
> run the first sunday each month. I created a RAID that finished
> first sync 3 hours ago, and since it`s now the first sunday in the
> month, a new resync started, which is a bit "to fast" IMO.
No, it started a check, not a resync.
> The script should make shure that the RAID`s creation date
>
Package: mdadm
Version: 3.1.4-1+8efb9d1ubuntu4
Severity: wishlist
Forwarding this feature request that was added to Ubuntu a while ago, and still
seems to be present in the mdadm packages.
The original report is available at https://launchpad.net/bugs/188482
Tor Henning Ueland Wrote:
> As i can
5 matches
Mail list logo
