Update btrfs-progs to newer version?btrfs errors and ro mount after last apt update

    • OMV 3.x
    • Resolved

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Update btrfs-progs to newer version?btrfs errors and ro mount after last apt update

      Hi,

      Currently using OMV 3.0.59, it has btrfs-progs 3.17;
      running OMV as KVM vm in Proxmox-VE Virtual Environment 4.4-5/c43015a5;
      The harddrives are passthrough to OMV

      The newest btrfs-progs is version 4.9
      if trying to install the new btrfs-progs via apt, it will try to uninstall openmediavault.

      Is there a way to have the newest btrfs-progs live with the openmediavault 3 together?
      Why we still have this old version within openmediavault 3?

      With the current setup, after the last apt update, I got lots of errors with btrfs and it is forcing my harddrive to mount as ro time to time:


      Shell-Script

      1. [ 3.385277] BTRFS info (device sdb1): disk space caching is enabled
      2. [ 3.385279] BTRFS info (device sdb1): has skinny extents
      3. [ 3.388703] BTRFS info (device sdd1): disk space caching is enabled
      4. [ 3.388704] BTRFS info (device sdd1): has skinny extents
      5. [ 3.389532] BTRFS info (device sda1): disk space caching is enabled
      6. [ 3.389533] BTRFS info (device sda1): has skinny extents
      7. [ 3.390574] BTRFS info (device sdc1): disk space caching is enabled
      8. [ 3.390576] BTRFS info (device sdc1): has skinny extents
      9. [ 3.419708] BTRFS info (device sdd1): bdev /dev/sdd1 errs: wr 0, rd 159, flush 0, corrupt 0, gen 0
      10. [ 3.449176] BTRFS info (device sdc1): bdev /dev/sdc1 errs: wr 11, rd 64, flush 0, corrupt 0, gen 0
      11. [ 3.458517] BTRFS info (device sda1): bdev /dev/sda1 errs: wr 0, rd 85, flush 0, corrupt 0, gen 0
      12. [ 3.476531] BTRFS info (device sdb1): bdev /dev/sdb1 errs: wr 51, rd 0, flush 0, corrupt 0, gen 0
      13. [ 3.681998] systemd-journald[482]: Received request to flush runtime journal from PID 1
      14. [ 3.976493] BTRFS info (device sdb1): checking UUID tree
      15. [ 4.532431] RPC: Registered named UNIX socket transport module.
      16. [ 4.532433] RPC: Registered udp transport module.
      17. [ 4.532434] RPC: Registered tcp transport module.
      18. [ 4.532434] RPC: Registered tcp NFSv4.1 backchannel transport module.
      19. [ 4.535112] FS-Cache: Loaded
      20. [ 4.539993] FS-Cache: Netfs 'nfs' registered for caching
      21. [ 4.545611] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
      22. [ 141.091842] sd 0:0:0:0: [sda] tag#13 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
      23. [ 141.091862] sd 0:0:0:0: [sda] tag#13 Sense Key : Illegal Request [current]
      24. [ 141.091868] sd 0:0:0:0: [sda] tag#13 Add. Sense: Invalid field in cdb
      25. [ 141.091873] sd 0:0:0:0: [sda] tag#13 CDB: Read(10) 28 00 3c 9e 7a 00 00 08 00 00
      26. [ 141.091877] blk_update_request: critical target error, dev sda, sector 1017018880
      27. [ 141.091932] BTRFS error (device sda1): bdev /dev/sda1 errs: wr 0, rd 86, flush 0, corrupt 0, gen 0
      28. [ 141.092484] sd 0:0:0:0: [sda] tag#12 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
      29. [ 141.092486] sd 0:0:0:0: [sda] tag#12 Sense Key : Illegal Request [current]
      30. [ 141.092487] sd 0:0:0:0: [sda] tag#12 Add. Sense: Invalid field in cdb
      31. [ 141.092489] sd 0:0:0:0: [sda] tag#12 CDB: Read(10) 28 00 3c 9e 72 00 00 08 00 00
      32. [ 141.092490] blk_update_request: critical target error, dev sda, sector 1017016832
      33. [ 141.092526] BTRFS error (device sda1): bdev /dev/sda1 errs: wr 0, rd 87, flush 0, corrupt 0, gen 0
      34. [ 141.758149] sd 0:0:0:0: [sda] tag#5 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
      35. [ 141.758153] sd 0:0:0:0: [sda] tag#5 Sense Key : Illegal Request [current]
      36. [ 141.758155] sd 0:0:0:0: [sda] tag#5 Add. Sense: Invalid field in cdb
      37. [ 141.758157] sd 0:0:0:0: [sda] tag#5 CDB: Read(10) 28 00 3c 9f 8a 00 00 08 00 00
      38. [ 141.758159] blk_update_request: critical target error, dev sda, sector 1017088512
      39. [ 141.758210] BTRFS error (device sda1): bdev /dev/sda1 errs: wr 0, rd 88, flush 0, corrupt 0, gen 0
      40. [ 141.790872] sd 0:0:0:0: [sda] tag#9 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
      41. [ 141.790875] sd 0:0:0:0: [sda] tag#9 Sense Key : Illegal Request [current]
      42. [ 141.790877] sd 0:0:0:0: [sda] tag#9 Add. Sense: Invalid field in cdb
      43. [ 141.790879] sd 0:0:0:0: [sda] tag#9 CDB: Read(10) 28 00 3c 9f c2 00 00 08 00 00
      44. [ 141.790881] blk_update_request: critical target error, dev sda, sector 1017102848
      45. [ 141.790932] BTRFS error (device sda1): bdev /dev/sda1 errs: wr 0, rd 89, flush 0, corrupt 0, gen 0
      46. [ 142.004908] sd 0:0:0:0: [sda] tag#4 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
      47. [ 142.004912] sd 0:0:0:0: [sda] tag#4 Sense Key : Illegal Request [current]
      48. [ 142.004914] sd 0:0:0:0: [sda] tag#4 Add. Sense: Invalid field in cdb
      49. [ 142.004926] sd 0:0:0:0: [sda] tag#4 CDB: Read(10) 28 00 3c 9f f2 00 00 08 00 00
      50. [ 142.004928] blk_update_request: critical target error, dev sda, sector 1017115136
      51. [ 142.004972] BTRFS error (device sda1): bdev /dev/sda1 errs: wr 0, rd 90, flush 0, corrupt 0, gen 0
      52. [ 142.005032] sd 0:0:0:0: [sda] tag#7 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
      53. [ 142.005034] sd 0:0:0:0: [sda] tag#7 Sense Key : Illegal Request [current]
      54. [ 142.005035] sd 0:0:0:0: [sda] tag#7 Add. Sense: Invalid field in cdb
      55. [ 142.005036] sd 0:0:0:0: [sda] tag#7 CDB: Read(10) 28 00 3c a0 0a 00 00 08 00 00
      56. [ 142.005037] blk_update_request: critical target error, dev sda, sector 1017121280
      57. [ 142.005078] BTRFS error (device sda1): bdev /dev/sda1 errs: wr 0, rd 91, flush 0, corrupt 0, gen 0
      58. [ 142.183284] sd 0:0:0:0: [sda] tag#7 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
      59. [ 142.183287] sd 0:0:0:0: [sda] tag#7 Sense Key : Illegal Request [current]
      60. [ 142.183294] sd 0:0:0:0: [sda] tag#7 Add. Sense: Invalid field in cdb
      61. [ 142.183296] sd 0:0:0:0: [sda] tag#7 CDB: Read(10) 28 00 3c a0 4a 00 00 08 00 00
      62. [ 142.183298] blk_update_request: critical target error, dev sda, sector 1017137664
      63. [ 142.183347] BTRFS error (device sda1): bdev /dev/sda1 errs: wr 0, rd 92, flush 0, corrupt 0, gen 0
      64. [ 142.403454] sd 0:0:0:0: [sda] tag#3 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
      65. [ 142.403457] sd 0:0:0:0: [sda] tag#3 Sense Key : Illegal Request [current]
      66. [ 142.403459] sd 0:0:0:0: [sda] tag#3 Add. Sense: Invalid field in cdb
      67. [ 142.403462] sd 0:0:0:0: [sda] tag#3 CDB: Read(10) 28 00 3c a0 6a 00 00 08 00 00
      68. [ 142.403464] blk_update_request: critical target error, dev sda, sector 1017145856
      69. [ 142.403512] BTRFS error (device sda1): bdev /dev/sda1 errs: wr 0, rd 93, flush 0, corrupt 0, gen 0
      70. [ 167.053365] sd 0:0:0:1: [sdd] tag#1 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
      71. [ 167.053369] sd 0:0:0:1: [sdd] tag#1 Sense Key : Illegal Request [current]
      72. [ 167.053371] sd 0:0:0:1: [sdd] tag#1 Add. Sense: Invalid field in cdb
      73. [ 167.053374] sd 0:0:0:1: [sdd] tag#1 CDB: Read(10) 28 00 00 a3 54 00 00 08 00 00
      74. [ 167.053376] blk_update_request: critical target error, dev sdd, sector 10703872
      75. [ 167.053425] BTRFS error (device sdd1): bdev /dev/sdd1 errs: wr 0, rd 160, flush 0, corrupt 0, gen 0
      76. [ 167.152374] sd 0:0:0:1: [sdd] tag#13 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
      77. [ 167.152378] sd 0:0:0:1: [sdd] tag#13 Sense Key : Illegal Request [current]
      78. [ 167.152380] sd 0:0:0:1: [sdd] tag#13 Add. Sense: Invalid field in cdb
      79. [ 167.152383] sd 0:0:0:1: [sdd] tag#13 CDB: Read(10) 28 00 00 a3 dc 00 00 08 00 00
      80. [ 167.152386] blk_update_request: critical target error, dev sdd, sector 10738688
      81. [ 167.152438] BTRFS error (device sdd1): bdev /dev/sdd1 errs: wr 0, rd 161, flush 0, corrupt 0, gen 0
      82. [ 167.239771] sd 0:0:0:1: [sdd] tag#8 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
      83. [ 167.239793] sd 0:0:0:1: [sdd] tag#8 Sense Key : Illegal Request [current]
      84. [ 167.239800] sd 0:0:0:1: [sdd] tag#8 Add. Sense: Invalid field in cdb
      85. [ 167.239804] sd 0:0:0:1: [sdd] tag#8 CDB: Read(10) 28 00 00 a4 1c 00 00 08 00 00
      86. [ 167.239808] blk_update_request: critical target error, dev sdd, sector 10755072
      87. [ 167.239860] BTRFS error (device sdd1): bdev /dev/sdd1 errs: wr 0, rd 162, flush 0, corrupt 0, gen 0
      Display All

      All the harddrive was fine before he last apt update, also the smart information shows ok for them.

      The post was edited 5 times, last by rynax ().

    • Hi, the output is

      Shell-Script

      1. linux-image-4.8.0-2-grsec-amd64:
      2. Installed: (none)
      3. Candidate: 4.8.15-1+grsec201612151923+1~bpo8+1
      4. Package pin: 4.8.15-1+grsec201612151923+1~bpo8+1
      5. Version table:
      6. 4.8.15-1+grsec201612151923+1~bpo8+1 500
      7. 100 http://httpredir.debian.org/debian/ jessie-backports/main amd64 Packages
      8. linux-image-3.16.0-4-amd64:
      9. Installed: 3.16.36-1+deb8u2
      10. Candidate: 3.16.36-1+deb8u2
      11. Package pin: (not found)
      12. Version table:
      13. 3.16.39-1 500
      14. 500 http://ftp.au.debian.org/debian/ jessie/main amd64 Packages
      15. *** 3.16.36-1+deb8u2 500
      16. 500 http://security.debian.org/ jessie/updates/main amd64 Packages
      17. 100 /var/lib/dpkg/status
      18. 3.16.7-ckt25-2 500
      19. 500 http://ftp.au.debian.org/debian/ jessie-updates/main amd64 Packages
      20. linux-image-4.7.0-0.bpo.1-amd64:
      21. Installed: (none)
      22. Candidate: 4.7.8-1~bpo8+1
      23. Package pin: 4.7.8-1~bpo8+1
      24. Version table:
      25. 4.7.8-1~bpo8+1 500
      26. 100 http://httpredir.debian.org/debian/ jessie-backports/main amd64 Packages
      27. linux-image-4.7.0-0.bpo.1-amd64-unsigned:
      28. Installed: (none)
      29. Candidate: (none)
      30. Package pin: (not found)
      31. Version table:
      32. linux-image-4.8.0-0.bpo.2-amd64-unsigned:
      33. Installed: (none)
      34. Candidate: 4.8.11-1~bpo8+1
      35. Package pin: 4.8.11-1~bpo8+1
      36. Version table:
      37. 4.8.11-1~bpo8+1 500
      38. 100 http://httpredir.debian.org/debian/ jessie-backports/main amd64 Packages
      39. linux-image-rt-amd64:
      40. Installed: (none)
      41. Candidate: 4.8+77~bpo8+1
      42. Package pin: 4.8+77~bpo8+1
      43. Version table:
      44. 4.8+77~bpo8+1 500
      45. 100 http://httpredir.debian.org/debian/ jessie-backports/main amd64 Packages
      46. linux-image:
      47. Installed: (none)
      48. Candidate: (none)
      49. Version table:
      50. linux-image-amd64-dbg:
      51. Installed: (none)
      52. Candidate: 4.8+77~bpo8+1
      53. Package pin: 4.8+77~bpo8+1
      54. Version table:
      55. 4.8+77~bpo8+1 500
      56. 100 http://httpredir.debian.org/debian/ jessie-backports/main amd64 Packages
      57. 3.16+63 500
      58. 500 http://ftp.au.debian.org/debian/ jessie/main amd64 Packages
      59. linux-image-4.8.0-0.bpo.2-amd64-dbg:
      60. Installed: (none)
      61. Candidate: 4.8.11-1~bpo8+1
      62. Package pin: 4.8.11-1~bpo8+1
      63. Version table:
      64. 4.8.11-1~bpo8+1 500
      65. 100 http://httpredir.debian.org/debian/ jessie-backports/main amd64 Packages
      66. linux-image-rt-amd64-dbg:
      67. Installed: (none)
      68. Candidate: 4.8+77~bpo8+1
      69. Package pin: 4.8+77~bpo8+1
      70. Version table:
      71. 4.8+77~bpo8+1 500
      72. 100 http://httpredir.debian.org/debian/ jessie-backports/main amd64 Packages
      73. linux-image-4.8.0-0.bpo.2-rt-amd64-unsigned:
      74. Installed: (none)
      75. Candidate: 4.8.11-1~bpo8+1
      76. Package pin: 4.8.11-1~bpo8+1
      77. Version table:
      78. 4.8.11-1~bpo8+1 500
      79. 100 http://httpredir.debian.org/debian/ jessie-backports/main amd64 Packages
      80. linux-image-4.8.0-0.bpo.2-rt-amd64-dbg:
      81. Installed: (none)
      82. Candidate: 4.8.11-1~bpo8+1
      83. Package pin: 4.8.11-1~bpo8+1
      84. Version table:
      85. 4.8.11-1~bpo8+1 500
      86. 100 http://httpredir.debian.org/debian/ jessie-backports/main amd64 Packages
      87. linux-image-4.8.0-0.bpo.2-rt-amd64:
      88. Installed: (none)
      89. Candidate: 4.8.11-1~bpo8+1
      90. Package pin: 4.8.11-1~bpo8+1
      91. Version table:
      92. 4.8.11-1~bpo8+1 500
      93. 100 http://httpredir.debian.org/debian/ jessie-backports/main amd64 Packages
      94. linux-image-2.6:
      95. Installed: (none)
      96. Candidate: (none)
      97. Package pin: (not found)
      98. Version table:
      99. linux-image-amd64:
      100. Installed: 4.8+77~bpo8+1
      101. Candidate: 4.8+77~bpo8+1
      102. Package pin: 4.8+77~bpo8+1
      103. Version table:
      104. *** 4.8+77~bpo8+1 500
      105. 100 http://httpredir.debian.org/debian/ jessie-backports/main amd64 Packages
      106. 100 /var/lib/dpkg/status
      107. 3.16+63 500
      108. 500 http://ftp.au.debian.org/debian/ jessie/main amd64 Packages
      109. linux-image-grsec-amd64:
      110. Installed: (none)
      111. Candidate: 11~bpo8+1
      112. Package pin: 11~bpo8+1
      113. Version table:
      114. 11~bpo8+1 500
      115. 100 http://httpredir.debian.org/debian/ jessie-backports/main amd64 Packages
      116. linux-image-2.6-rt:
      117. Installed: (none)
      118. Candidate: (none)
      119. Package pin: (not found)
      120. Version table:
      121. linux-image-4.8.0-0.bpo.2-amd64:
      122. Installed: 4.8.11-1~bpo8+1
      123. Candidate: 4.8.11-1~bpo8+1
      124. Package pin: 4.8.11-1~bpo8+1
      125. Version table:
      126. *** 4.8.11-1~bpo8+1 500
      127. 100 http://httpredir.debian.org/debian/ jessie-backports/main amd64 Packages
      128. 100 /var/lib/dpkg/status
      129. linux-image-3.16.0-4-amd64-dbg:
      130. Installed: (none)
      131. Candidate: 3.16.39-1
      132. Package pin: (not found)
      133. Version table:
      134. 3.16.39-1 500
      135. 500 http://ftp.au.debian.org/debian/ jessie/main amd64 Packages
      136. 3.16.36-1+deb8u2 500
      137. 500 http://security.debian.org/ jessie/updates/main amd64 Packages
      138. 3.16.7-ckt25-2 500
      139. 500 http://ftp.au.debian.org/debian/ jessie-updates/main amd64 Packages
      Display All
      uname gives me this

      Linux omv3-kvm 4.8.0-0.bpo.2-amd64 #1 SMP Debian 4.8.11-1~bpo8+1 (2016-12-14) x86_64 GNU/Linux

      So looks like I'm already using the backports kernel?

      The post was edited 1 time, last by rynax ().

    • sfu420 wrote:

      I'm using the 4.7 Backport Kernel with btrfs-progs 4.7.3 (also installed from backport repo) without any issue.
      You should not update the kernel to 4.8 until btrfs-progs 4.8.x is not available in the backport repo.
      Yep this could be the problem,
      so I should use apt-get -t jessie-backports install btrfs-tools to install the 4.7 version;
      also downgrade back to 4.7 kernel
    • rynax wrote:

      sfu420 wrote:

      I'm using the 4.7 Backport Kernel with btrfs-progs 4.7.3 (also installed from backport repo) without any issue.
      You should not update the kernel to 4.8 until btrfs-progs 4.8.x is not available in the backport repo.
      Yep this could be the problem,so I should use apt-get -t jessie-backports install btrfs-tools to install the 4.7 version;
      also downgrade back to 4.7 kernel
      Yes, it should solve your problem.
    • So I have 4.7 kernel and btrfs-tools 4.7 now.
      still getting the same errors while doing snapraid sync, having erros on all drivers, just like the ones in op:

      Shell-Script

      1. [ 101.476173] BTRFS error (device sdc1): bdev /dev/sdc1 errs: wr 12, rd 98, flush 0, corrupt 0, gen 0
      2. [ 101.478138] sd 0:0:0:2: [sdc] tag#12 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
      3. [ 101.478145] sd 0:0:0:2: [sdc] tag#12 Sense Key : Illegal Request [current]
      4. [ 101.478147] sd 0:0:0:2: [sdc] tag#12 Add. Sense: Invalid field in cdb
      5. [ 101.478152] sd 0:0:0:2: [sdc] tag#12 CDB: Write(10) 2a 00 0e 7e aa b8 00 08 00 00
      6. [ 101.478154] blk_update_request: critical target error, dev sdc, sector 243182264
      7. ...
      8. [ 102.166396] BTRFS error (device sda1): bdev /dev/sda1 errs: wr 5, rd 144, flush 0, corrupt 0, gen 0
      9. [ 105.824667] sd 0:0:0:3: [sdb] tag#1 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
      10. [ 105.824686] sd 0:0:0:3: [sdb] tag#1 Sense Key : Illegal Request [current]
      11. [ 105.824692] sd 0:0:0:3: [sdb] tag#1 Add. Sense: Invalid field in cdb
      12. [ 105.824710] sd 0:0:0:3: [sdb] tag#1 CDB: Write(16) 8a 00 00 00 00 00 00 54 8f e0 00 00 08 00 00 00
      13. [ 105.824715] blk_update_request: critical target error, dev sdb, sector 5541856
      14. [ 105.825169] BTRFS error (device sdb1): bdev /dev/sdb1 errs: wr 97, rd 0, flush 0, corrupt 0, gen 0
      Display All
    • All right, it's not omv/btrfs problem, it's Proxmox-VE 4.4 problem.

      Recently updatd from 4.3 to 4.4, and it's having issue with
      virtio_scsi

      Btrfs error and critical target errors with KVM disk passthrough

      forum.rockstor.com/t/btrfs-err…m-disk-passthrough/2573/4

      Proxmox 4.4 virtio_scsi regression

      forum.proxmox.com/threads/prox…io_scsi-regression.31471/

      This reminds me of do not use a virtualized storage if it is going to be a production system.
      Complex system means much more risks.
      Like this problem, it is corrupting my data.
    • rynax wrote:

      This reminds me of do not use a virtualized storage if it is going to be a production system.
      Complex system means much more risks.
      Like this problem, it is corrupting my data.
      This must not be a very common problem since there aren't a ton of people posting about it on proxmox. I use disk passthrough on all of my proxmox boxes and haven't seen an issue. My main server even has one 8TB drive passed through to an OMV 3.x VM and is formatted with btrfs.

      sfu420 wrote:

      It's much better to use an LSI HBA with PCI Passthrough than using disk passthrough...
      On ESXi, I would agree with that but I have found just the opposite on Proxmox. And yes, I have two LSI HBAs in my server.
      omv 4.0.11 arrakis | 64 bit | 4.13 backports kernel | omvextrasorg 4.1.0
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • rynax wrote:

      sfu420 wrote:

      I'm using the 4.7 Backport Kernel with btrfs-progs 4.7.3 (also installed from backport repo) without any issue.
      You should not update the kernel to 4.8 until btrfs-progs 4.8.x is not available in the backport repo.
      Yep this could be the problem,so I should use apt-get -t jessie-backports install btrfs-tools to install the 4.7 version;
      also downgrade back to 4.7 kernel
      I too had installed the 4.8 kernel from Jessie backports and this is how I installed the 4.7 kernel image for anyone else struggling:

      Source Code

      1. echo 'Acquire::Check-Valid-Until false;' > /etc/apt/apt.conf.d/archive
      2. echo 'deb http://snapshot.debian.org/archive/debian/20161024T110554Z/ jessie-backports main contrib non-free' > /etc/apt/sources.list.d/debian-snapshot.list
      3. apt-get update
      4. apt-get install linux-image-4.7.0-0.bpo.1-amd64

      I also had to change the default boot kernel by working out which menuentry I wanted from /boot/ggrub/grub.cfg, editing /etc/default/grub to change the GRUB_DEFAULT menuentry to 2 (in my case) and running update-grub. I know this should be easily done using OMV's GUI and the Kernel tab under OMV-Extras, but the GUI appears to have a bug and my /etc/default/grub file was slowly 'eaten' each time I pressed the 'Set as default boot kernel' button' :!:

      Sophie x