This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-zesty

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1706243

Title:
  Stranded with ENODEV after mdadm --readonly

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  == SRU Justification ==
  The bug reporter was trying to turn on the RAID journal.  One of the steps
  is to set the device readonly.  This did not work as planned, or indeed at
  all. After the first --readonly, all requests for the device report
  "No such device or address" until a reboot, though /proc/mdstat says the
  device is still there.

  This bug is fixed by mainline commit 065e519e71b2c1f41936cce75b46b5ab34adb588,
  which is in mainline as of 4.12-rc1.  The commit was also cc'd to stable, but
  upstream 4.10 is EOL, so that is the reason for the SRU request.

  == Fix ==
  commit 065e519e71b2c1f41936cce75b46b5ab34adb588
  Author: NeilBrown <ne...@suse.com>
  Date:   Thu Apr 6 11:16:33 2017 +0800

      md: MD_CLOSING needs to be cleared after called md_set_readonly or
  do_md_stop

  == Regression Potential ==
  This commit was also cc'd to stable and accepted, so additional upstream 
review
  was performed.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.



  Please backport upstream fix.

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=v4.12.3&id=065e519e71b2c1f41936cce75b46b5ab34adb588
  ---
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   trent     10668 F...m pulseaudio
   /dev/snd/pcmC0D0p:   trent     10668 F...m pulseaudio
   /dev/snd/controlC0:  trent     10668 F.... pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=848108cd-a607-494c-a6ea-626267ed0a12
  InstallationDate: Installed on 2014-12-23 (944 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   p11p1     no wireless extensions.

   lo        no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 002: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB 
Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=7afb765b-b26b-44cc-ace1-654320cd85b2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware                             1.157.11
  RfKill:

  Tags:  xenial xenial
  Uname: Linux 4.10.0-26-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to xenial on 2017-07-01 (24 days ago)
  UserGroups: adm audio cdrom dip glftpd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 06/16/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0808
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B250M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0808:bd06/16/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1706243/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to