@Steve, Sorry for the delay in my reply.
As far as I can remember, the map is lost when we pivot to the *new* rootfs.
The lost map is then reconstructed by calling the rebuild code. This map is
what is needed for the proper reconstruction of the raid array.
--
You received this bug
is created for maverick
and can apply also for lucid.
Thanks!
** Patch added: mdadm_lp_bug_fixes.debdiff
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/136252/+attachment/2139759/+files/mdadm_lp_bug_fixes.debdiff
** Changed in: mdadm (Ubuntu)
Assignee: Surbhi Palande (csurbhi
@ceg,
yes, the hostname part is no longer needed for the newer mdadm. We don't need
any of the patches for natty. They only apply to older mdadm version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: os-prober (Ubuntu Natty)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/764893
Title:
os-prober: does not detect Ubuntu in btrfs subvolume
--
** Changed in: os-prober (Ubuntu Natty)
Status: New = Confirmed
** Changed in: os-prober (Ubuntu Natty)
Assignee: (unassigned) = Surbhi Palande (csurbhi)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
** Changed in: friendly-recovery (Ubuntu)
Status: New = Confirmed
** Changed in: friendly-recovery (Ubuntu)
Assignee: (unassigned) = Surbhi Palande (csurbhi)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
@Steve Langasek,
Thanks for your insight. I agree with your comments. I have uploaded a patch to
plymouth::details/plugin.c to print only the last line of the password prompt.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
During boot, Ubuntu uses the details plugin to display the entered
password prompt and the bullets. The trouble is that in initramfs the
cryptroot script makes the password prompt _two_ lined. The details
plugin clears only the current line and then overwrites the password
prompt string on the
** Changed in: btrfs-tools (Ubuntu)
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/750209
Title:
btrfs does a full partition check on each boot
--
ubuntu-bugs
** Changed in: plymouth (Ubuntu Natty)
Assignee: (unassigned) = Surbhi Palande (csurbhi)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/566818
Title:
Cryptsetup passphrase prompt during boot
** Attachment added: lucid-proposed-debdiff
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/665185/+attachment/1981801/+files/lucid-proposed-debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: maverick-proposed-debdiff
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/665185/+attachment/1981802/+files/maverick-proposed-debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: maverick-proposed-debdiff
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/665185/+attachment/1977640/+files/maverick-proposed-debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: lucid-proposed-debdiff
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/665185/+attachment/1977641/+files/lucid-proposed-debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: debdiff of initscripts between 1) existing natty source
and 2) patch given by the bug reporter applied
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/665185/+attachment/1949315/+files/debdiff_665185
--
You received this bug notification because you are a member
** Changed in: mdadm (Ubuntu Natty)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/728435
Title:
raid1 boot degraded mode fails
--
ubuntu-bugs mailing list
After an email exchange with Neil Brown, identified that using mdadm
-IRs instead of mdadm -Ars will fix this issue. So made the necessary
change in the initramfs/init-premount/mdadm script - as a fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This is the first version of the patch. Also trying to figure out if an
array can be simply started without stopping when there are no more
member devices available.
** Patch added: 0001-Stop-an-array-before-trying-to-scan-assemble-it.patch
The following workaround can be used for the time being:
1) mdadm -S /dev/array that you want to start in degraded mode
and then
2) mdadm --assemble --scan --run
This should start the array that you want in degraded mode (for now)
--
You received this bug notification because you are a member
@Joseph Salisbury,
Can you attach the wireshark trace in case of a failure _and_ in case of
success. We need to find out the difference in the data that the windows client
is sending to the samba server. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server
Comparing the success and the failure logs attached by the bug reporter,
I can see the following difference:
Success-log:
[2010/03/11 08:05:57, 3] libsmb/ntlmssp.c:ntlmssp_server_auth(739)
Got user=[someuser] domain=[SOMEDOMAIN] workstation=[SERVER3] len1=24 len2=24
[2010/03/11 08:05:57, 2]
@Raphaël Pinson, please rewrite your patch making it generic for /var/* or
/usr/* and the ! has_option (mnt, nobootwait, FALSE) condition, as discussed
on irc. Also to request a merge of your patch, please follow the instructions
here:
@Joseph Salisbury,
Can you attach the wireshark trace in case of a failure _and_ in case of
success. We need to find out the difference in the data that the windows client
is sending to the samba server. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Comparing the success and the failure logs attached by the bug reporter,
I can see the following difference:
Success-log:
[2010/03/11 08:05:57, 3] libsmb/ntlmssp.c:ntlmssp_server_auth(739)
Got user=[someuser] domain=[SOMEDOMAIN] workstation=[SERVER3] len1=24 len2=24
[2010/03/11 08:05:57, 2]
** Changed in: mountall (Ubuntu)
Assignee: (unassigned) = Surbhi Palande (csurbhi)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/654545
Title:
mountall does not honor nobootwait flag on /var
@Joseph Salisbury, yes please do attach the logs with the log level set
to 10. It will give us more voluminous output.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
https://bugs.launchpad.net/bugs/526464
Title:
@Joseph Salisbury, yes please do attach the logs with the log level set
to 10. It will give us more voluminous output.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/526464
Title:
intermittent
@Joseph Salisbury, can you please attach the relevant logs in /var/log/samba/
after doing the following:
1) In /etc/samba/smb.conf set the debuglevel =10 (in the
Debugging/Accounting section, before log =something)
--
You received this bug notification because you are a member of
@Joseph Salisbury, can you please attach the relevant logs in /var/log/samba/
after doing the following:
1) In /etc/samba/smb.conf set the debuglevel =10 (in the
Debugging/Accounting section, before log =something)
--
You received this bug notification because you are a member of
A revision number like -0ubuntuX is used only when we take Debian
packages and add our own patches on top of it. Ubuntu's upstart is not
based on Debian's version of upstart. Hence the naming scheme is -X
instead of the -0ubuntuX.
** Changed in: upstart (Ubuntu Natty)
Status: Confirmed =
Sorry for marking the bug invalid before. After discussing the bug with
mvo, realized the confusion that might occur as debian's upstart (which
is based on Ubuntu) also has the same revision number. Unless the
debian's upstart has the same source (with no modification at all) the
version numbers
So sorry about the previous comment.. I confirmed that both in Lucid and
in upstream, WRITE is followed by a COMMIT in *vfs_write()*. This does
mean that the data is ultimately put on the backing store and that
vfs_write waits for that to happen before it returns back (iff the
O_SYNC flag is set -
I did a test to write 100 blocks using dd with and without oflag=sync
and saw the same result in wireshark, namely of getting a WRITE-COMMIT
sequence. However it seems to me that this sequence is because of the
nfs writeback code rather than vfs_write(). In Lucid, it appears that
vfs_write() does
** Changed in: linux (Ubuntu)
Assignee: Surbhi Palande (csurbhi) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/437574
Title:
BUG: unable to handle kernel NULL pointer
@Joseph, the semantics of O_DIRECT are different that O_SYNC.
In case of NFS, O_DIRECT *bypasses the page cache on the client* entirely. The
NFS protocol does not support passing this flag to the server. By passing the
client side cache could have other side effects like not being able to
** Changed in: nfs-utils (Ubuntu)
Assignee: Surbhi Palande (csurbhi) = (unassigned)
** Changed in: nfs-utils (Ubuntu Lucid)
Assignee: Surbhi Palande (csurbhi) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
In the current upstream code, I think that instead of the WRITE
operation where arg.stable=FILE_SYNC, a COMMIT operation occurs so that
the server commits the requested data to the stable storage. I think
that this should be good enough to simulate the FILE_SYNC behavior as
the requested data will
Adding a few patches for mdadm auto assembly to work. Seen in the ppa
requested for testing.
** Patch added: 0001-map-rebuild-map-if-it-doesn-t-exist.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/136252/+attachment/1819903/+files/0001-map-rebuild-map-if-it-doesn-t-exist.patch
--
** Patch added: 0002-maps-Fix-bugs-in-map_read.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/136252/+attachment/1819904/+files/0002-maps-Fix-bugs-in-map_read.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: 0003-mapfile-fix-bug-in-testing-for-var-run-mdadm.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/136252/+attachment/1819905/+files/0003-mapfile-fix-bug-in-testing-for-var-run-mdadm.patch
--
You received this bug notification because you are a member of Ubuntu
** Patch added:
0004-mapfile-allow-the-path-name-to-the-device-to-be-empt.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/136252/+attachment/1819910/+files/0004-mapfile-allow-the-path-name-to-the-device-to-be-empt.patch
--
You received this bug notification because you are a
** Patch added: 0005-mapfile-Fix-off-by-one-error-in-RebuildMap.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/136252/+attachment/1819911/+files/0005-mapfile-Fix-off-by-one-error-in-RebuildMap.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Patch added: 0007-fix-add_dev-handling-of-broken-links.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/136252/+attachment/1819912/+files/0007-fix-add_dev-handling-of-broken-links.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Patch added:
0008-Fix-an-error-when-assembling-arrays-that-are-in-the-.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/136252/+attachment/1819921/+files/0008-Fix-an-error-when-assembling-arrays-that-are-in-the-.patch
--
You received this bug notification because you are a
** Patch added:
0010-mapfile-when-rebuilding-choose-an-appropriate-name-i.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/136252/+attachment/1819923/+files/0010-mapfile-when-rebuilding-choose-an-appropriate-name-i.patch
--
You received this bug notification because you are a
** Patch added: Adding this code renaming patch, to make the porting of the
rest of the patches from Neil Brown's repository easy.
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/136252/+attachment/1819924/+files/0011-Rename-open_mddev-to-create_mddev.patch
--
You received this bug
** Patch added:
0012-Incremental-lock-against-multiple-concurrent-additio.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/136252/+attachment/1819925/+files/0012-Incremental-lock-against-multiple-concurrent-additio.patch
--
You received this bug notification because you are a
** Patch added:
0009-Adjust-major-number-testing-to-allow-for-extended-mi.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/136252/+attachment/1819922/+files/0009-Adjust-major-number-testing-to-allow-for-extended-mi.patch
--
You received this bug notification because you are a
** Patch added: 0013-Add-locks-for-Manage_runstop.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/136252/+attachment/1819926/+files/0013-Add-locks-for-Manage_runstop.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Patch added:
0014-Bug-fixing-for-mdadm-map-file-reading-and-dev-name-c.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/136252/+attachment/1819927/+files/0014-Bug-fixing-for-mdadm-map-file-reading-and-dev-name-c.patch
--
You received this bug notification because you are a
** Patch added: 0015-Partition-creation-logic-fixing.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/136252/+attachment/1819928/+files/0015-Partition-creation-logic-fixing.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Patch added: 0017-Fixed-locking.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/136252/+attachment/1819929/+files/0017-Fixed-locking.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: 0018-Initramfs-to-set-hostname-for-autoassembly.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/136252/+attachment/1819934/+files/0018-Initramfs-to-set-hostname-for-autoassembly.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Patch added: initramfs change to set the hostname
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/136252/+attachment/1819935/+files/0018-Initramfs-to-set-hostname-for-autoassembly.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Patch added: 0019-Always-set-homehost-if-not-specified.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/136252/+attachment/1819936/+files/0019-Always-set-homehost-if-not-specified.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
1) The ppa requested for testing consists of these patches. They are needed for
the proper working of mdadm auto assembly.
2) Also for the mdadm autoassembly to work properly, the following needs
sponsorship for maverick and lucid:
https://code.launchpad.net/~csurbhi/+junk/initramfs.mdadm.fixes.
** Patch added: 0001-map-rebuild-map-if-it-doesn-t-exist.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/615186/+attachment/1819969/+files/0001-map-rebuild-map-if-it-doesn-t-exist.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Patch added: 0002-maps-Fix-bugs-in-map_read.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/615186/+attachment/1819971/+files/0002-maps-Fix-bugs-in-map_read.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: 0003-mapfile-fix-bug-in-testing-for-var-run-mdadm.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/615186/+attachment/1819972/+files/0003-mapfile-fix-bug-in-testing-for-var-run-mdadm.patch
--
You received this bug notification because you are a member of Ubuntu
** Patch added:
0004-mapfile-allow-the-path-name-to-the-device-to-be-empt.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/615186/+attachment/1819977/+files/0004-mapfile-allow-the-path-name-to-the-device-to-be-empt.patch
--
You received this bug notification because you are a
** Patch added: 0005-mapfile-Fix-off-by-one-error-in-RebuildMap.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/615186/+attachment/1819993/+files/0005-mapfile-Fix-off-by-one-error-in-RebuildMap.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Patch added: 0007-fix-add_dev-handling-of-broken-links.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/615186/+attachment/1820017/+files/0007-fix-add_dev-handling-of-broken-links.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Patch added:
0008-Fix-an-error-when-assembling-arrays-that-are-in-the-.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/615186/+attachment/1820018/+files/0008-Fix-an-error-when-assembling-arrays-that-are-in-the-.patch
--
You received this bug notification because you are a
** Patch added:
0009-Adjust-major-number-testing-to-allow-for-extended-mi.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/615186/+attachment/1820019/+files/0009-Adjust-major-number-testing-to-allow-for-extended-mi.patch
--
You received this bug notification because you are a
** Patch added:
0010-mapfile-when-rebuilding-choose-an-appropriate-name-i.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/615186/+attachment/1820020/+files/0010-mapfile-when-rebuilding-choose-an-appropriate-name-i.patch
--
You received this bug notification because you are a
** Patch added: 0011-Rename-open_mddev-to-create_mddev.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/615186/+attachment/1820021/+files/0011-Rename-open_mddev-to-create_mddev.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Patch added:
0012-Incremental-lock-against-multiple-concurrent-additio.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/615186/+attachment/1820022/+files/0012-Incremental-lock-against-multiple-concurrent-additio.patch
--
You received this bug notification because you are a
** Patch added: 0013-Add-locks-for-Manage_runstop.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/615186/+attachment/1820023/+files/0013-Add-locks-for-Manage_runstop.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Patch added:
0014-Bug-fixing-for-mdadm-map-file-reading-and-dev-name-c.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/615186/+attachment/1820024/+files/0014-Bug-fixing-for-mdadm-map-file-reading-and-dev-name-c.patch
--
You received this bug notification because you are a
** Patch added: 0015-Partition-creation-logic-fixing.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/615186/+attachment/1820025/+files/0015-Partition-creation-logic-fixing.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Patch added: 0018-Initramfs-to-set-hostname-for-autoassembly.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/615186/+attachment/1820027/+files/0018-Initramfs-to-set-hostname-for-autoassembly.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Patch added: 0019-Always-set-homehost-if-not-specified.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/615186/+attachment/1820046/+files/0019-Always-set-homehost-if-not-specified.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Patch added: 0017-Fixed-locking.patch
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/615186/+attachment/1820026/+files/0017-Fixed-locking.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
1) The ppa requested for testing consists of these patches. They are needed for
the proper working of mdadm auto assembly.
2) Also for the mdadm autoassembly to work properly, the following needs
sponsorship for maverick and lucid:
https://code.launchpad.net/~csurbhi/+junk/initramfs.mdadm.fixes.
Upstream patch applied to maverick-updates. Please consider merging.
** Attachment added: debdiff of util-linux between 1) maverick-updates and 2)
upstream patch applied to maverick-updates (edit)
** Attachment added: debdiff of util-linux between 1)natty and 2) upstream
patch applied to natty
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/579858/+attachment/1808541/+files/debdiff_natty-unreleased
--
You received this bug notification because you are a member of Ubuntu
** Changed in: util-linux (Ubuntu Lucid)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/579858
Title:
umount segfault on shutdown when unmounting autofs
Please do consider this patch for Lucid.
** Attachment added: debdiff of util-linux between 1) lucid-updates and 2)
upstream patch applied to lucid-updates
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/579858/+attachment/1800875/+files/debdiff
--
You received this bug
@ceg, wont the uuid for the raid array be different from that of the
individual raid member device?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/531240
Title:
silently breaking raid: root
much for your help. Remember that this is a test package and your
help is extremely appreciated :) I have tested these packages on test virtual
machines.
** Changed in: mdadm (Ubuntu)
Assignee: (unassigned) = Surbhi Palande (csurbhi)
** Changed in: mdadm (Ubuntu)
Status: Triaged
Hi All, Thanks a lot for your insightful comments and making Ubuntu
better. I have done the fixes mostly, based on these comments. The
patches are based on the source code in neil-browns git repository and a
few initramfs fixes which are applicable to Ubuntu (which are again
based on the bugs on
Call for testing mdadm 2.7.1 autoassembly.
For hitherto Ubuntu releases the mdadm package shall stay at 2.7.1
However Natty would have mdadm at 3.4.1. This document is intended to
test the mdadm fixes for 2.7.1. Here is the rough procedure that needs
to be followed:
Testing auto-assembly of
@Jools, @ceg, Thanks a lot for your insightful comments and making
Ubuntu better. I have done the fixes mostly, based on these comments.
The patches are based on the source code in neil-browns git repository
and a few initramfs fixes which are applicable to Ubuntu (which are
again based on the
@Stephan B,
Yes, you are absolutely correct. I have done something similar in initramfs
kept at the above mentioned ppa. Thanks a lot for the valuable suggestion.
Please do let me know if the ppa works for you or not :)
--
maps file not getting copied from initramfs to real rootfs (loosing
these are only for maverick. I shall be uploading the
ones based for lucid soon enough! Thanks again!
** Changed in: mdadm (Ubuntu)
Status: Confirmed = In Progress
** Changed in: mdadm (Ubuntu)
Assignee: (unassigned) = Surbhi Palande (csurbhi)
--
[-UUIDudev] mdadm.conf without ARRAY
Call for testing mdadm 2.7.1 autoassembly - For anyone who is seeing
this bug.
For hitherto Ubuntu releases the mdadm package shall stay at 2.7.1
However Natty would have mdadm at 3.4.1. This document is intended to
test the mdadm fixes for 2.7.1. Here is the rough procedure that needs
to be
.
Thanks very much for your help. Remember that this is a test package and your
help is extremely appreciated :) I have tested these packages on test virtual
machines.
** Changed in: mdadm (Ubuntu)
Status: New = Confirmed
** Changed in: mdadm (Ubuntu)
Assignee: (unassigned) = Surbhi
that this is a test package and your
help is extremely appreciated :) I have tested these packages on test virtual
machines.
** Changed in: mdadm (Ubuntu)
Status: Confirmed = In Progress
** Changed in: mdadm (Ubuntu)
Assignee: (unassigned) = Surbhi Palande (csurbhi)
--
[-UUIDudev] mdadm
@tombert, your bug is different than this bug. Please do open another
bug for the same and run apport-collect for it. Thanks!
--
mdadm update is scaring me: YOUR SYSTEM IS NOW UNBOOTABLE!
https://bugs.launchpad.net/bugs/652327
You received this bug notification because you are a member of Ubuntu
-2.6.7).
Meanwhile, I shall also look at what can be done about devices instead
of uuids. Thanks a lot for filing this bug!
** Changed in: mdadm (Ubuntu)
Status: New = Confirmed
** Changed in: mdadm (Ubuntu)
Assignee: (unassigned) = Surbhi Palande (csurbhi)
--
mdadm update is scaring
RnSC, by an large the work that I have done is merging the latest mdadm from
Debian with Ubuntu related fixes. Also, I have cherry picked fixes from Neil
Browns mdadm git repository and also created one other Ubuntu's mdadm related
fix for initramfs - so that the auto assembly of md devices
** Patch added: debdiff of debian mdadm-3.4.1 and ubuntu's mdadm-3.4.1 merged
version
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/603582/+attachment/1699779/+files/oldUbuntu_newUbuntu.debdiff
--
Please merge mdadm 3.1.2-2 (main) from Debian stable (main)
the above patch is a debdiff between ubuntu 2.7.1 and merged
mdadm-3.4.1. Reattaching the two debdiffs again with appropriate names.
--
Please merge mdadm 3.1.2-2 (main) from Debian stable (main)
https://bugs.launchpad.net/bugs/603582
You received this bug notification because you are a member
** Patch added: debdiff of debian-3.1.4 vs Ubuntus merged 3.1.4 mdadm version
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/603582/+attachment/1699788/+files/debian_newUbuntu.debdiff
--
Please merge mdadm 3.1.2-2 (main) from Debian stable (main)
https://bugs.launchpad.net/bugs/603582
** Patch added: debdiff of Ubuntu's old 2.7.1 mdadm vs Ubuntu's newly merged
3.1.4 mdadm
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/603582/+attachment/1699797/+files/oldUbuntu_newUbuntu.debdiff
--
Please merge mdadm 3.1.2-2 (main) from Debian stable (main)
I have lightly tested these patches against Ubuntus maverick installer and also
post installation.
Please do let me know the review and any changes that are required. Thanks a
lot!
--
Please merge mdadm 3.1.2-2 (main) from Debian stable (main)
https://bugs.launchpad.net/bugs/603582
You
I also have a few tested patches for auto assembly to work properly.
Shall add them on top of this, once these debdiffs are reviewed and
accepted!
--
Please merge mdadm 3.1.2-2 (main) from Debian stable (main)
https://bugs.launchpad.net/bugs/603582
You received this bug notification because you
** Summary changed:
- Please merge mdadm 3.1.2-2 (main) from Debian stable (main)
+ Please merge mdadm 3.1.4-1 (main) from Debian stable (main)
--
Please merge mdadm 3.1.4-1 (main) from Debian stable (main)
https://bugs.launchpad.net/bugs/603582
You received this bug notification because you
** Branch linked: lp:~csurbhi/+junk/cryptsetup-initramfs.fix
--
crypted lvm on raid does not boot (lvm device name ... does not begin with
/dev/mapper/)
https://bugs.launchpad.net/bugs/577239
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The error message that you get here
cryptsetup: lvm device name (/dev/disk/by-uuid/...) does not begin with
/dev/mapper/ comes due to the fact that the
conf/conf.d/cryptroot in initramfs contains a line with source=UUID=uuid
instead of the intended source=/dev/mapper/vol-group-path if there is
1 - 100 of 394 matches
Mail list logo
