This still isn't fixed as best I can follow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/320638
Title:
hot-add/remove in mixed (IDE/SATA/USB/SD-card/...) RAIDs with device
mapper on top =>
** Changed in: linux
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/320638
Title:
hot-add/remove in mixed (IDE/SATA/USB/SD-card/...) RAIDs with device
@Phillip Susi / comment #23: Did you actually read what I wrote? :)
I was *NOT* advocating backup by having multiple RAID disks constantly
connected to the array and in sync. It is completely obvious to me that a hot
running copy of data is NOT a backup.
I was advocating the following
RAID is *not* a backup solution. If you delete or overwrite a file,
then it's done on both disks, so you can't recover. If you want a rapid
and coherent backup, use LVM and take a snapshot and back that up.
Also note that this commentary really isn't helping to fix the bug.
--
You received
Also, keep on mind that the most commonly used personal computers
nowadays don't even *support* adding multiple disks of the same type:
Laptops. They only have one HD slot, so I *must* use USB to attach the
second.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
What you people are forgetting is that RAID1 is in fact the PERFECT backup
solution:
It takes a low level copy of the whole system while the system is *running*,
and as opposed to cp/rsync, the copy is *coherent*:
Programmers do NOT design software to be robust against their files being
** Changed in: linux
Status: Fix Released = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/320638
Title:
hot-add/remove in mixed (IDE/SATA/USB/SD-card/...) RAIDs with device
The resolution of fix released is incorrect: the kernel bug is still
present. The debian bug was closed due to age rather due to being
fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/320638
** Changed in: linux
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/320638
Title:
hot-add/remove in mixed (IDE/SATA/USB/SD-card/...) RAIDs with device
I don't know, how it behaves with USB3.
Same data corruption as well, unfortunately.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/320638
Title:
hot-add/remove in mixed (IDE/SATA/USB/SD-card/...)
** Description changed:
Problem: md changes max_sector setting of an already running and busy md
device, when a (hotplugable) device is added or removed. However, the
device mapper and filesystem layer on top of the raid can not (always?)
cope with that.
Observations:
* bio too big
I'm using SATA drives for LVM on RAID 1. RAID is configured with
internal bitmap, so resyncing is quite fast.
In order to do the best kind of backup, I replace my drives to keep backups of
complete systems.
There is a very good reason for this, since in the case of a complete desaster
I simply
This is an upstream issue in kernel / handling nested block device (lvm on top
of mdadm).
It would be interesting to know if the patches to recursively call
merge_bvec_fn became a reality nowadays. [1]
It's best to ping linux-raid mailing list to query if anything changed with
respect to this
Never mind, Neil recently replied about the state of the art w.r.t. to this bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624343#106
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/320638
** Description changed:
- Note: Bug is also present when hot-plugging USB, Firewire etc. devices.
+ Problem: md changes max_sector setting of an already running and busy md
+ device, when a (hotplugable) device is added or removed. However, the a
+ device mapper and filesystem layer on top of the
** Also affects: mdadm
Importance: Undecided
Status: New
** Changed in: mdadm
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/320638
Title:
hot-add/remove in
16 matches
Mail list logo
