On 04/03/2015 02:43 PM, Nicholas A. Bellinger wrote:
On Fri, 2015-04-03 at 11:41 -0400, Dan Lane wrote:
I recently rebuilt my storage server (again) using Fedora 21 Server
(64-bit). Once everything was up and running I built out my target
configuration and confirmed it was working. This was using the
original Kernel 3.17.4.
At this point I decided to update my update my server. Once I was
done with all the updates, I found that target now refuses to start.
Running "journalctl -xe" shows the following errors:
Apr 03 02:24:36 labsan1.home.lan kernel: dev[ffff8800c8ffa000]: Passed
optimal_sectors 8192 cannot be greater than hw_max_sectors: 512
block/data: Cannot set attribute optimal_sectors: [Errno 22] Invalid
argument, skipped
Apr 03 02:24:40 labsan1.home.lan target[1149]: Storage Object
block/data: Cannot find attribute: fabric_max_sectors, skipped
Apr 03 02:24:40 labsan1.home.lan systemd[1]: target.service: main
process exited, code=exited, status=255/n/a
Apr 03 02:24:40 labsan1.home.lan systemd[1]: Failed to start Restore
LIO kernel target configuration.
-- Subject: Unit target.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit target.service has failed.
--
-- The result is failed.
uname -a:
Linux labsan1.home.lan 3.19.3-200.fc21.x86_64 #1 SMP Thu Mar 26
21:39:42 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
This looks like a -fb specific bug. Even if setting an attribute fails,
it should not abort bringing up the device. Adding Andy CC'.
OK I'll go tone this down. FWIW right now we don't abort configuring LIO
halfway through but we do fail target.service.
Regards -- Andy
--
To unsubscribe from this list: send the line "unsubscribe target-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
