Hello,
mdadm supports set of different metadata. Intel metadata is a part of it
(called IMSM). We (as Intel) are submitted a lot of fixes and features, all are
validated and tested. Beside upstream testing, we have our internal test scope,
focused on IMSM aspects. I can say with certainty that u
yes, it is resolved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868708
Title:
mdmon: device descriptor is not closed
To manage notifications about this bug go to:
https://bugs.launchpad.net/mda
yes, it is resolved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/112
Title:
mdmonitor doesn't start recovery immediately
To manage notifications about this bug go to:
https://bugs.launchpad.n
Public bug reported:
Please update mdadm package for Hirsuteto latest upstream release.
mdadm-4.2-rc1 was released for this moment.
mdadm-4.2 on track.
I will notify if mdadm 4.2 will become available.
** Affects: mdadm (Ubuntu)
Importance: Undecided
Status: New
** Tags: vroc
--
mdadm-4.2-rc-1 has been released officially.
Could you update the mdadm version?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890248
Title:
update mdadm for focal
To manage notifications about th
Hello,
fix for second problem has been accepted upstream:
https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=a64f1263a56bd8653267c1a9800daa0bc993a743
Mariusz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
mdadm-4.2 not yet released.
Feel free to close it if not applicable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890162
Title:
Update mdadm for bionic
To manage notifications about this bug go t
mdadm-4.2 not released yet.
Feel free to close it if not applicable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890248
Title:
update mdadm for focal
To manage notifications about this bug go to
Hi,
Patch has been accepted upstream:
https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=cab9c67d461c65a1138359f9f6d39636466b90e4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/112
Tit
Hi,
sorry copy-paste mistake, here the correct ones:
https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=e2308733910a157b0a4d4e78721f239d44b91a24
https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=007087d0898a045901e4e120296e6d9b845b20a6
--
You received this bug notificat
Hi,
Patches have been accepted upstream:
https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=e2308733910a157b0a4d4e78721f239d44b91a24
https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=cab9c67d461c65a1138359f9f6d39636466b90e4
--
You received this bug notification because
** Tags added: vroc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885191
Title:
[Focal] Installation Fails with "Invalid dep_id" when using Intel VROC
To manage notifications about this bug go to:
For 5.8 this is a simple backport with one conflict caused by function
md_make_request() renamed to md_submit_bio(). Then it can be easily
cherry picked to 5.4 but will need a change to use
generic_{start,end}_io_acct() instead of disk_{start,end}_io_acct(). I
can send you the backported patches if
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891151
Title:
md: improve IO accounting
To manage notifications about this bug go
** Tags added: vroc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758282
Title:
[INTEL UBUNTU 18.04] RAID reshape hangs after OS reboot
To manage notifications about this bug go to:
https://bugs.l
** Tags added: vroc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887143
Title:
mdmonitor closes mdstat fd if is empty
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubun
** Tags added: vroc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868708
Title:
mdmon: device descriptor is not closed
To manage notifications about this bug go to:
https://bugs.launchpad.net/mdad
** Tags added: vroc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811228
Title:
Mdadm allows to change the name of the volume to empty and not trim
whitespaces.
To manage notifications about thi
** Tags added: vroc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/112
Title:
mdmonitor doesn't start recovery immediately
To manage notifications about this bug go to:
https://bugs.launchpad.ne
** Tags added: vroc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890162
Title:
Update mdadm for bionic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mdad
** Tags added: vrco
** Tags removed: vrco
** Tags added: vroc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890248
Title:
update mdadm for focal
To manage notifications about this bug go to:
http
** Tags added: vroc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887372
Title:
Cannot create lvm upon IMSM raid array
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubun
** Tags added: vroc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887640
Title:
IMSM: finish recovery when drive with rebuild fails
To manage notifications about this bug go to:
https://bugs.launc
Public bug reported:
Currently reported IO stats may be incorrect or missing.
This adds correct statistics about in-flight IOs and IO processing time,
interpreted e.g. in iostat as await, svctm, aqu-sz and %util.
Commit:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?
Public bug reported:
Please update mdadm package for focal to latest upstream.
mdadm-4.2 in on way but no release date was committed yet.
Upstream contains a lot of various fixes for problems with specific hardware or
system configuration.
Also there are some fixes for sporadic bugs related with
** Description changed:
Mdadm version available in bionic was released in march 2018. Since it many
various fixes has been added.
The most common and important of them (from IMSM site) are already reported:
https://bugs.launchpad.net/oem-priority/+bug/1868708
https://bugs.launchpad.net/ub
Public bug reported:
Mdadm version available in bionic was released in march 2018. Since it many
various fixes has been added.
The most common and important of them (from IMSM site) are already reported:
https://bugs.launchpad.net/oem-priority/+bug/1868708
https://bugs.launchpad.net/ubuntu/+sourc
** Description changed:
mdmonitor reacts on md events, it pools on /proc/mdstat file. Those
events are generated if a change on any mddevice is observed in kernel.
This is done asynchronously and can be caused by user space process
(mdadm called by udev or user), or by kernel itself (drive
Hi,
mdmonitor needs to deal with other tasks, issue still in development.
Thanks, Mariusz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/112
Title:
mdmonitor doesn't start recovery immediately
Public bug reported:
mdmonitor reacts on md events, it pools on /proc/mdstat file. Those
events are generated if a change on any mddevice is observed in kernel.
This is done asynchronously and can be caused by user space process
(mdadm called by udev or user), or by kernel itself (drive is removed
Public bug reported:
Current version of mdadm doesn't have second fix for raid10.
Mdmon is not able do handle end recovery if drive was disconnected while
rebuild.
Steps to reproduce:
1. Create RAID10 and wait for resync.
#mdadm --create /dev/md/imsm0 --metadata=imsm --raid-devices=4 /dev/sda
** Summary changed:
- Cannot create lvm opon IMSM raid array
+ Cannot create lvm upon IMSM raid array
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887372
Title:
Cannot create lvm upon IMSM raid a
Public bug reported:
The issue has been observed on 2.3.7 (Ubuntu 20.04).
Reported to lvm team:
https://bugzilla.redhat.com/show_bug.cgi?id=1855251
Steps to Reproduce:
1. Create IMSM raid array:
#mdadm -CR imsm -e imsm -n2 /dev/nvme[01]n1
#mdadm -CR vol -l1 -n2 /dev/nvme[01]n1 -z 5G
2. Create lv
Hello,
The main issue is in development, we need to deal with module reload and
descriptor handling.
The second one can be easily workaround by using systemctl service
(systemctl mdmonitor restart) instead of command line. Here error
handling is needed instead of quiet fail.
I will notify if any
Public bug reported:
There was a change in mdadm to fix issue when md_mod is reloaded (not a case
for ubuntu because md_mod is build-in). Commit:
https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=52209d6ee1183581e148791cf6ee4d60a0193b1d
The fix prevents mdmonitor from occupying mds
Hi, issue is fixed by:
https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=91c97c5432028875db5f8abeddb5cb5f31902001
Thanks,
Mariusz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868708
T
Public bug reported:
When device disappears from the system "mdadm -If" is triggered by udev
and drive is removed from the corresponding array and container. The
missing close() in metadata manager (mdmon) causes that userspace
handler to the device is still opened (can be tracked by lsof -p
).
F
Hi,
We have two issues here:
1. mdraid stuff is always included in initrd even system isn't on raid( ubuntu
specific).
2. grow continue service is not restarted after switch root( to be fixed in
upstream)
First one should be detected and managed in ubuntu installer. This is how it is
done in ot
Hi,
New version of ledmon has been released.
https://github.com/intel/ledmon/releases/tag/0.94
Thanks,
Mariusz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855254
Title:
Update ledmon to 0.94 t
Private bug reported:
New version of ledmon (v0.94) may contain following features:
- NPEM support
Ledmon’s extension including feature above is in active development. Final
version will be included in GitHub repository:
https://github.com/intel/ledmon
Pull request will be triggered on this Bug
Hi,
the issue is fixed in bionic-proposed.
Thanks
Mariusz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811228
Title:
Mdadm allows to change the name of the volume to empty and not trim
whitesp
Hi,
the issue is fixed in bionic-proposed.
Thanks,
Mariusz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811795
Title:
Mdadm: external metadata arrays and containers are removed incorrectly
To ma
Hi,
The issue is fixed in PPA.
Thanks, Mariusz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811228
Title:
Mdadm allows to change the name of the volume to empty and not trim
whitespaces.
To ma
Hi,
Here test steps:
1. Create IMSM Container:
mdadm -CR imsm0 -e imsm -n 2 /dev/sd[bc]
2. Create IMSM level 0 Array:
mdadm -CR vol0 -l 0 -n 2 /dev/sd[bc]
3. Wait for resync to complete
mdadm --wait /dev/md/vol0
4. Read /proc/mdstat and check /dev/md/ directory
cat /proc/mdstat
l
Private bug reported:
Steps to reproduce:
1. Create IMSM container on 2 SATA disks.
2. Create R0 IMSM volume
3. Wait for resync to complete.
4. Fail one of disks
Expected result:
R0 Array should disappear form /proc/mdstat.
Actual result:
R0 array is visible in mdstat, link to container in /
45 matches
Mail list logo
