On 04/02/2016 02:17, Shaohua Li wrote:
On Mon, Feb 01, 2016 at 12:00:36AM +0100, Eric Valette wrote:
On 28/01/2016 20:52, Eric Valette wrote:
On 28/01/2016 19:25, Shaohua Li wrote:
If really needed can rebuild a 4.4 kernel and boot it. What do you mean
by special config? I can send you my kernel .config once rebuild
(oldconfig from 4.1.16)
Linux nas2 4.4.1 #1 SMP Sun Jan 31 23:46:26 CET 2016 x86_64 GNU/Linux
Nothing useful. Did you try stop the array and reassemble it in 4.4 and check
if resync runs? I can only imagine the reboot script didn't clean shutdown the
array and trigger the issue. A stop/reassemble circle will tell us if this is
the issue.
If the issue was in the script it would happen with all the kernel
version no? Si far 3.14, 3.18, 4.1 works correctly (when upgrading).
Only 4.4 fails.
4.4 in fact seems to fails to boot the first time I boot it. As I have
no console normally, I have to shut down via power button and then it
resync. I can understand this behavior but not
1) that the resync fails each time and
2) that it fails to boot the first time I change for a 4.4 kernel.
-- eric
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html