[Bug 550131] Re: maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig)
@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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/550131 Title: maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/550131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 136252] Re: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails)
Debdiff of all patches fixing bugs for: *) autoassembly of raid arrays This will also as a good side effect: *) choose the correct device name (also necessary for correct auto assembly). *) report the appropriate meta data information. Please do consider this for mdadm-2.6.7.x. The debdiff 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) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/136252 Title: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 136252] Re: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails)
@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. https://bugs.launchpad.net/bugs/136252 Title: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 764893] Re: os-prober: does not detect Ubuntu in btrfs subvolume
** 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 764893] Re: 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://bugs.launchpad.net/bugs/764893 Title: os-prober: does not detect Ubuntu in btrfs subvolume -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 575469] Re: recovery mode mounts filesystems read-write rather than read-only
** 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://bugs.launchpad.net/bugs/575469 Title: recovery mode mounts filesystems read-write rather than read-only -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 566818] Re: Cryptsetup passphrase prompt during boot: every character typed repeats the prompt
@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. https://bugs.launchpad.net/bugs/566818 Title: Cryptsetup passphrase prompt during boot: every character typed repeats the prompt -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 566818] Re: Cryptsetup passphrase prompt during boot: every character typed repeats the prompt
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 cleared line. The effect of this is that the _second_ line in the password prompt always gets overwritten. Thus on every key input, the first line overwrites the previously displayed second line (printed due to the previous key press). Thus you see the first line repeated over and over again with every keypress. The solution to this could be one of the following: 1) make the password prompt single line 2) clear the whole screen instead of clearing a single line before writing the password prompt. 3) append the bullets instead of the line 4) clear in some way the previous line. IMHO, the disadvantage of 1,3,4 is that in case you boot with plymouth:debug, the password prompt would still be repeated (as you will have debug messages interleaved and what you clear is different than what you intended to). Clearing the screen would on the other hand cause a clearing of screen with every keypress and wipe out any debug messages that you could be interested in. Shall soon upload a patch with a appropriate solution. -- 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: every character typed repeats the prompt -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 750209] Re: btrfs does a full partition check on each boot
** 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 566818] Re: Cryptsetup passphrase prompt during boot: every character typed repeats the prompt
** 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: every character typed repeats the prompt -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665185] Re: /etc/init.d/sendsigs fails to kill some processes
** 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. https://bugs.launchpad.net/bugs/665185 Title: /etc/init.d/sendsigs fails to kill some processes -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665185] Re: /etc/init.d/sendsigs fails to kill some processes
** 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. https://bugs.launchpad.net/bugs/665185 Title: /etc/init.d/sendsigs fails to kill some processes -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665185] Re: /etc/init.d/sendsigs fails to kill some processes
** 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. https://bugs.launchpad.net/bugs/665185 Title: /etc/init.d/sendsigs fails to kill some processes -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665185] Re: /etc/init.d/sendsigs fails to kill some processes
** 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. https://bugs.launchpad.net/bugs/665185 Title: /etc/init.d/sendsigs fails to kill some processes -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665185] Re: /etc/init.d/sendsigs fails to kill some processes
** 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 of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/665185 Title: /etc/init.d/sendsigs fails to kill some processes -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 728435] Re: raid1 boot degraded mode fails
** 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 728435] Re: raid1 boot degraded mode fails
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/728435 Title: raid1 boot degraded mode fails -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 728435] Re: raid1 boot degraded mode fails
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 https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/728435/+attachment/1910502/+files/0001-Stop-an-array-before-trying-to-scan-assemble-it.patch -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 728435] Re: raid1 boot degraded mode fails
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 of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/728435 Title: raid1 boot degraded mode fails -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 526464] Re: intermittent authentication: check_ntlm_password: Authentication for user [someuser] - [someuser] FAILED with error NT_STATUS_ACCESS_DENIED
@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 Team, which is subscribed to samba in ubuntu. https://bugs.launchpad.net/bugs/526464 Title: intermittent authentication: check_ntlm_password: Authentication for user [someuser] - [someuser] FAILED with error NT_STATUS_ACCESS_DENIED -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 526464] Re: intermittent authentication: check_ntlm_password: Authentication for user [someuser] - [someuser] FAILED with error NT_STATUS_ACCESS_DENIED
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] auth/auth.c:check_ntlm_password(309) check_ntlm_password: authentication for user [someuser] - [someuser] - [SOMEDOMAIN+someuser] succeeded -- Failure-log: [2010/01/27 19:02:21, 3] libsmb/ntlmssp.c:ntlmssp_server_auth(739) Got user=[] domain=[] workstation=[SERVER3] len1=1 len2=0 [2010/01/27 19:02:22, 2] auth/auth.c:check_ntlm_password(319) check_ntlm_password: Authentication for user [someuser] - [someuser] FAILED with error NT_STATUS_ACCESS_DENIED The domain seems missing here? -- Perhaps the wireshark trace will tell us better. Please attach the corresponding logs in case of failure _and_ success along with the wireshark output, so that tracing will be easier! Thanks! -- 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: intermittent authentication: check_ntlm_password: Authentication for user [someuser] - [someuser] FAILED with error NT_STATUS_ACCESS_DENIED -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 654545] Re: mountall does not honor nobootwait flag on /var/* and /usr/* filesystems
@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: https://wiki.ubuntu.com/DistributedDevelopment/Documentation Thanks! -- 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/* and /usr/* filesystems -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 526464] Re: intermittent authentication: check_ntlm_password: Authentication for user [someuser] - [someuser] FAILED with error NT_STATUS_ACCESS_DENIED
@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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/526464 Title: intermittent authentication: check_ntlm_password: Authentication for user [someuser] - [someuser] FAILED with error NT_STATUS_ACCESS_DENIED -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 526464] Re: intermittent authentication: check_ntlm_password: Authentication for user [someuser] - [someuser] FAILED with error NT_STATUS_ACCESS_DENIED
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] auth/auth.c:check_ntlm_password(309) check_ntlm_password: authentication for user [someuser] - [someuser] - [SOMEDOMAIN+someuser] succeeded -- Failure-log: [2010/01/27 19:02:21, 3] libsmb/ntlmssp.c:ntlmssp_server_auth(739) Got user=[] domain=[] workstation=[SERVER3] len1=1 len2=0 [2010/01/27 19:02:22, 2] auth/auth.c:check_ntlm_password(319) check_ntlm_password: Authentication for user [someuser] - [someuser] FAILED with error NT_STATUS_ACCESS_DENIED The domain seems missing here? -- Perhaps the wireshark trace will tell us better. Please attach the corresponding logs in case of failure _and_ success along with the wireshark output, so that tracing will be easier! Thanks! -- 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 authentication: check_ntlm_password: Authentication for user [someuser] - [someuser] FAILED with error NT_STATUS_ACCESS_DENIED -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 654545] Re: mountall does not honor nobootwait flag on /var/* and /usr/* filesystems
** 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/* and /usr/* filesystems -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 526464] Re: intermittent authentication: check_ntlm_password: Authentication for user [someuser] - [someuser] FAILED with error NT_STATUS_ACCESS_DENIED
@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: intermittent authentication: check_ntlm_password: Authentication for user [someuser] - [someuser] FAILED with error NT_STATUS_ACCESS_DENIED -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 526464] Re: intermittent authentication: check_ntlm_password: Authentication for user [someuser] - [someuser] FAILED with error NT_STATUS_ACCESS_DENIED
@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 authentication: check_ntlm_password: Authentication for user [someuser] - [someuser] FAILED with error NT_STATUS_ACCESS_DENIED -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 526464] Re: intermittent authentication: check_ntlm_password: Authentication for user [someuser] - [someuser] FAILED with error NT_STATUS_ACCESS_DENIED
@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 Ubuntu Server Team, which is subscribed to samba in ubuntu. https://bugs.launchpad.net/bugs/526464 Title: intermittent authentication: check_ntlm_password: Authentication for user [someuser] - [someuser] FAILED with error NT_STATUS_ACCESS_DENIED -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 526464] Re: intermittent authentication: check_ntlm_password: Authentication for user [someuser] - [someuser] FAILED with error NT_STATUS_ACCESS_DENIED
@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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/526464 Title: intermittent authentication: check_ntlm_password: Authentication for user [someuser] - [someuser] FAILED with error NT_STATUS_ACCESS_DENIED -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 693630] Re: upstart uses wrong Debian revision
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 = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/693630 Title: upstart uses wrong Debian revision -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 693630] Re: upstart uses wrong Debian revision
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 of upstart in Debian and upstart in Ubuntu should be different. In case the source is the same, then Ubuntu's upstart can have the same version has Debian's upstart (like a sync request). Either Debian or Ubuntu has to change their version number. So, marking the bug as confirmed! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/693630 Title: upstart uses wrong Debian revision -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 709392] Re: NFS client does not submit nfs_file_sync write requests when the file open call includes O_SYNC.
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 - which is the expected behavior) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/709392 Title: NFS client does not submit nfs_file_sync write requests when the file open call includes O_SYNC. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 709392] Re: NFS client does not submit nfs_file_sync write requests when the file open call includes O_SYNC.
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 not explicitly wait on a COMMIT to finish nor does it send stable=FILE_SYNC for a WRITE operation. So, I think that the expected synchronous behavior of O_SYNC flag or sync mounts is not seen in Lucid. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/709392 Title: NFS client does not submit nfs_file_sync write requests when the file open call includes O_SYNC. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 437574] Re: BUG: unable to handle kernel NULL pointer dereference at 0000000000000030
** 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 dereference at 0030 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 709392] Re: NFS client does not submit nfs_file_sync write requests when the file open call includes O_SYNC.
@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 optimize the rpc requests. O_DIRECT on its own does not give the guarantee of writing your data to the backing store like O_SYNC. O_SYNC on the other hand says that whatever data is requested for a write is synced to the backing store before the write operation returns. Its a synchronous write rather than an asynchronous one. A user may want to use O_SYNC but not O_DIRECT. Coupling the two together would give you the O_SYNC effect of putting data on the disk, but would have an unwanted effect on the client side cache and could most probably degrade performance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/709392 Title: NFS client does not submit nfs_file_sync write requests when the file open call includes O_SYNC. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 709392] Re: NFS client does not submit nfs_file_sync write requests when the file open call includes O_SYNC.
** 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. https://bugs.launchpad.net/bugs/709392 Title: NFS client does not submit nfs_file_sync write requests when the file open call includes O_SYNC. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 709392] Re: NFS client does not submit nfs_file_sync write requests when the file open call includes O_SYNC.
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 get committed to the stable storage as needed (both by fsync() and by the case when the file is opened with a sync flag) In case of Lucid, instead of a COMMIT a WRITE operation occurs. With the Lucid code, the trouble is that the arg stable does not get assigned to FILE_SYNC during a WRITE operation as it should when the file is opened with the sync flag (and also when a fsync is requested on the file) (Just writing my thoughts from what little I got to research) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/709392 Title: NFS client does not submit nfs_file_sync write requests when the file open call includes O_SYNC. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 136252] Re: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails)
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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/136252 Title: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 136252] Re: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails)
** 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. https://bugs.launchpad.net/bugs/136252 Title: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 136252] Re: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails)
** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/136252 Title: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 136252] Re: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails)
** 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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/136252 Title: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 136252] Re: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails)
** 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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/136252 Title: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 136252] Re: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails)
** 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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/136252 Title: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 136252] Re: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails)
** 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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/136252 Title: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 136252] Re: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails)
** 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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/136252 Title: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 136252] Re: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails)
** 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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/136252 Title: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 136252] Re: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails)
** 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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/136252 Title: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 136252] Re: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails)
** 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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/136252 Title: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 136252] Re: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails)
** 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 Ubuntu. https://bugs.launchpad.net/bugs/136252 Title: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 136252] Re: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails)
** 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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/136252 Title: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 136252] Re: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails)
** 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 Ubuntu. https://bugs.launchpad.net/bugs/136252 Title: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 136252] Re: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails)
** 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. https://bugs.launchpad.net/bugs/136252 Title: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 136252] Re: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails)
** 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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/136252 Title: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 136252] Re: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails)
** 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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/136252 Title: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 136252] Re: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails)
** 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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/136252 Title: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 136252] Re: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails)
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. Please do consider merging these patches for maverick and lucid. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/136252 Title: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 615186] Re: md_d0 array fabricated, prevents mounting md0 partitions
** 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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/615186 Title: md_d0 array fabricated, prevents mounting md0 partitions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 615186] Re: md_d0 array fabricated, prevents mounting md0 partitions
** 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. https://bugs.launchpad.net/bugs/615186 Title: md_d0 array fabricated, prevents mounting md0 partitions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 615186] Re: md_d0 array fabricated, prevents mounting md0 partitions
** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/615186 Title: md_d0 array fabricated, prevents mounting md0 partitions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 615186] Re: md_d0 array fabricated, prevents mounting md0 partitions
** 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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/615186 Title: md_d0 array fabricated, prevents mounting md0 partitions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 615186] Re: md_d0 array fabricated, prevents mounting md0 partitions
** 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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/615186 Title: md_d0 array fabricated, prevents mounting md0 partitions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 615186] Re: md_d0 array fabricated, prevents mounting md0 partitions
** 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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/615186 Title: md_d0 array fabricated, prevents mounting md0 partitions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 615186] Re: md_d0 array fabricated, prevents mounting md0 partitions
** 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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/615186 Title: md_d0 array fabricated, prevents mounting md0 partitions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 615186] Re: md_d0 array fabricated, prevents mounting md0 partitions
** 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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/615186 Title: md_d0 array fabricated, prevents mounting md0 partitions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 615186] Re: md_d0 array fabricated, prevents mounting md0 partitions
** 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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/615186 Title: md_d0 array fabricated, prevents mounting md0 partitions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 615186] Re: md_d0 array fabricated, prevents mounting md0 partitions
** 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 to Ubuntu. https://bugs.launchpad.net/bugs/615186 Title: md_d0 array fabricated, prevents mounting md0 partitions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 615186] Re: md_d0 array fabricated, prevents mounting md0 partitions
** 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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/615186 Title: md_d0 array fabricated, prevents mounting md0 partitions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 615186] Re: md_d0 array fabricated, prevents mounting md0 partitions
** 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 Ubuntu. https://bugs.launchpad.net/bugs/615186 Title: md_d0 array fabricated, prevents mounting md0 partitions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 615186] Re: md_d0 array fabricated, prevents mounting md0 partitions
** 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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/615186 Title: md_d0 array fabricated, prevents mounting md0 partitions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 615186] Re: md_d0 array fabricated, prevents mounting md0 partitions
** 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 Ubuntu. https://bugs.launchpad.net/bugs/615186 Title: md_d0 array fabricated, prevents mounting md0 partitions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 615186] Re: md_d0 array fabricated, prevents mounting md0 partitions
** 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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/615186 Title: md_d0 array fabricated, prevents mounting md0 partitions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 615186] Re: md_d0 array fabricated, prevents mounting md0 partitions
** 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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/615186 Title: md_d0 array fabricated, prevents mounting md0 partitions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 615186] Re: md_d0 array fabricated, prevents mounting md0 partitions
** 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. https://bugs.launchpad.net/bugs/615186 Title: md_d0 array fabricated, prevents mounting md0 partitions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 615186] Re: md_d0 array fabricated, prevents mounting md0 partitions
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. Please do consider merging these patches for maverick and lucid. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/615186 Title: md_d0 array fabricated, prevents mounting md0 partitions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 579858] Re: umount segfault on shutdown when unmounting autofs mountpoint
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) https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/579858/+attachment/1808539/+files/debdiff_maverick-proposed -- 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 mountpoint -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 579858] Re: umount segfault on shutdown when unmounting autofs mountpoint
** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/579858 Title: umount segfault on shutdown when unmounting autofs mountpoint -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 579858] Re: umount segfault on shutdown when unmounting autofs mountpoint
** 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 mountpoint -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 579858] Re: umount segfault on shutdown when unmounting autofs mountpoint
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 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 mountpoint -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 531240] Re: silently breaking raid: root raid_members opened as luks
@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 raid_members opened as luks -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 136252] Re: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails)
: (unassigned) = Surbhi Palande (csurbhi) ** Changed in: mdadm (Ubuntu) Status: Triaged = Confirmed ** Changed in: mdadm (Ubuntu) Status: Confirmed = In Progress -- [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails) https://bugs.launchpad.net/bugs/136252 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 136252] Re: [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails)
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 launchpad). Do let me know the output of the test ppas. At present these are only for maverick. I shall be uploading the ones based for lucid soon enough! Thanks again! -- [-UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot hotplug fails) https://bugs.launchpad.net/bugs/136252 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550131] Re: maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig)
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 your md array when your rootfs lies on it: 1)Install the mdadm package and initramfs package kept at: https://edge.launchpad.net/~csurbhi/+archive/mdadm-autoassembly 2)Run /usr/share/mdadm/mkconf and ensure that your /etc/mdadm/mdadm.conf has the array definition. a) Save your original initramfs in /boot itself by say /boot/initrd-old.img. b) Then run update-initramfs -c -k your-kernel-version. Store this iniramfs as /boot/initrd-new.img. We shall use this initramfs as a safety net. If you cannot boot with the auto-assembly fixes, then you should not land in a foot in your mouth situation. Through grub's edit menu, you can then resort to this safety net by editing the initrd=initrd-new.img (or if this does not work for some random reason then resort back to your older initrd=initrd-old.img) This way you will be sure that you can still boot your precious system. c) Now comment or remove the ARRAY definitions from your /etc/mdadm/mdadm.conf and once again run the same “update-initramfs -c -k your-kernel-version” to generate a brand new initramfs. 3)Run mdadm –detail –scan and note the UUIDs in the array. Note the hostname stored in your array. Does it not match with your real hostname? Then we can fix that at the initramfs prompt that you inevitably will land at if you try auto-assembly. Also note the device components that form the root md-device. Keep this paper for cross checking when you reboot 4)Reboot. 5)If you are at the initramfs prompt here are the things that you should first ensure: a) ls /bin/hostname /etc/hostname - are these files present? b) run “hostname”. Does this show you the hostname that your system is intended to have? Is it the same as the contents of /etc/hostname. c) ls /var/run – Is this dir there? If you answer yes to the above three questions, then things are so far so good. Now run the following command: mdadm –assemble -U uuid /dev/md-name dev-components-listed here Your mdadm –detail –scan that you ran previously should have given you the component names if you dont know it right now. Hopefully you have them listed on your paper. Eg in my case I ran: mdadm –assemble -U uuid /dev/md0 /dev/sda1 /dev/sdb1 Again run: mdadm –detail –scan md-device and verify that the uuids are indeed updated and the hostname reflects the hostname that is stored /etc/hostname. You can now press Ctr+D and you should come back to the root prompt. However you still need to test auto-assembly of your root md device. To do that simple reboot and you should not see the face of initramfs this time. You should land gently on your root prompt as you expected. If you do not see the light of the rootfs prompt this way or using this initramfs, then as mentioned earlier, please avail your saved initrd images through grub. Skip the further steps in this case. Update the launchpad bugs, saying you could not get to the root prompt with manual assembly as well. First we need to get manual assembly fixed for you before worrying about auto-assembly. But hopefully this wont be the case. 6)If in the first place your uuid matched with that of the hostname, because you already had updated the array meta data with the -U uuid command, then with these packages, ideally, you should directly see the root prompt without any problem. 7)If either way, you still see initramfs and are not seeing the root prompt, then kindly upload the following on the respective launchpad bugs related to mdadm: a) output of /var/run/mdadm.map b) output of /proc/mdstat. c) output of hostname (in initramfs) d) output of mdadm –detail –scan root-md-device (once you have assembled the array manually and have got at the root prompt) In order to save this output when you are the initramfs prompt you should copy these files in /dev/ and then manually assemble your array. Once you get to the root prompt, you would find these files in /dev/. Please attach these to the launchpad bugs and we can start debugging from there. For auto-assembly of your non root devices, this should not bring you to initramfs, unless you have the device mounted with a fs using fstab and are not using “nobootwait” in the options section for your fs. Once you are in the root fs, and your non -root array is not up with auto-assembly, then you can very easily attach the output of the /var/run/mdadm.map and /proc/mdstat. If needed, I will also post a mdadm package which will output a lot of verbose information, to find out what is exactly going wrong. 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. --
[Bug 550131] Re: maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig)
@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 bugs on launchpad). Do let me know the output of the test ppas. At present these are only for maverick. I shall be uploading the ones based for lucid soon enough! Thanks again :-) -- maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig) https://bugs.launchpad.net/bugs/550131 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550131] Re: maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig)
@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 state, race, misconfig) https://bugs.launchpad.net/bugs/550131 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 532960] Re: [-UUIDudev] mdadm.conf without ARRAY definition breaks reboot of new arrays
these packages on test virtual machines. Also, 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 launchpad). Do let me know the output of the test ppas. At present 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 definition breaks reboot of new arrays https://bugs.launchpad.net/bugs/532960 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 362938] Re: [-UUIDudev] Raid 1 configuration failed to start on boot
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 followed: Testing auto-assembly of your md array when your rootfs lies on it: 1)Install the mdadm package and initramfs package kept at: https://edge.launchpad.net/~csurbhi/+archive/mdadm-autoassembly 2)Run /usr/share/mdadm/mkconf and ensure that your /etc/mdadm/mdadm.conf has the array definition. a) Save your original initramfs in /boot itself by say /boot/initrd-old.img. b) Then run update-initramfs -c -k your-kernel-version. Store this iniramfs as /boot/initrd-new.img. We shall use this initramfs as a safety net. If you cannot boot with the auto-assembly fixes, then you should not land in a foot in your mouth situation. Through grub's edit menu, you can then resort to this safety net by editing the initrd=initrd-new.img (or if this does not work for some random reason then resort back to your older initrd=initrd-old.img) This way you will be sure that you can still boot your precious system. c) Now comment or remove the ARRAY definitions from your /etc/mdadm/mdadm.conf and once again run the same “update-initramfs -c -k your-kernel-version” to generate a brand new initramfs. 3)Run mdadm –detail –scan and note the UUIDs in the array. Note the hostname stored in your array. Does it not match with your real hostname? Then we can fix that at the initramfs prompt that you inevitably will land at if you try auto-assembly. Also note the device components that form the root md-device. Keep this paper for cross checking when you reboot 4)Reboot. 5)If you are at the initramfs prompt here are the things that you should first ensure: a) ls /bin/hostname /etc/hostname - are these files present? b) run “hostname”. Does this show you the hostname that your system is intended to have? Is it the same as the contents of /etc/hostname. c) ls /var/run – Is this dir there? If you answer yes to the above three questions, then things are so far so good. Now run the following command: mdadm –assemble -U uuid /dev/md-name dev-components-listed here Your mdadm –detail –scan that you ran previously should have given you the component names if you dont know it right now. Hopefully you have them listed on your paper. Eg in my case I ran: mdadm –assemble -U uuid /dev/md0 /dev/sda1 /dev/sdb1 Again run: mdadm –detail –scan md-device and verify that the uuids are indeed updated and the hostname reflects the hostname that is stored /etc/hostname. You can now press Ctr+D and you should come back to the root prompt. However you still need to test auto-assembly of your root md device. To do that simple reboot and you should not see the face of initramfs this time. You should land gently on your root prompt as you expected. If you do not see the light of the rootfs prompt this way or using this initramfs, then as mentioned earlier, please avail your saved initrd images through grub. Skip the further steps in this case. Update the launchpad bugs, saying you could not get to the root prompt with manual assembly as well. First we need to get manual assembly fixed for you before worrying about auto-assembly. But hopefully this wont be the case. 6)If in the first place your uuid matched with that of the hostname, because you already had updated the array meta data with the -U uuid command, then with these packages, ideally, you should directly see the root prompt without any problem. 7)If either way, you still see initramfs and are not seeing the root prompt, then kindly upload the following on the respective launchpad bugs related to mdadm: a) output of /var/run/mdadm.map b) output of /proc/mdstat. c) output of hostname (in initramfs) d) output of mdadm –detail –scan root-md-device (once you have assembled the array manually and have got at the root prompt) In order to save this output when you are the initramfs prompt you should copy these files in /dev/ and then manually assemble your array. Once you get to the root prompt, you would find these files in /dev/. Please attach these to the launchpad bugs and we can start debugging from there. For auto-assembly of your non root devices, this should not bring you to initramfs, unless you have the device mounted with a fs using fstab and are not using “nobootwait” in the options section for your fs. Once you are in the root fs, and your non -root array is not up with auto-assembly, then you can very easily attach the output of the /var/run/mdadm.map and /proc/mdstat. If needed, I will also post a mdadm package which will output a lot of verbose information, to find out what is exactly going wrong. Thanks very much for your help. Remember that this is a test package and your help is extremely appreciated :) I have tested these
[Bug 615186] Re: md_d0 array fabricated, prevents mounting md0 partitions
a mdadm package which will output a lot of verbose information, to find out what is exactly going wrong. 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 Palande (csurbhi) ** Changed in: mdadm (Ubuntu) Status: Confirmed = In Progress -- md_d0 array fabricated, prevents mounting md0 partitions https://bugs.launchpad.net/bugs/615186 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 541058] Re: [-UUIDudev] mdadm fails to automatically assemble raid during boot (without mdadm.conf)
information, to find out what is exactly going wrong. 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: Confirmed = In Progress ** Changed in: mdadm (Ubuntu) Assignee: (unassigned) = Surbhi Palande (csurbhi) -- [-UUIDudev] mdadm fails to automatically assemble raid during boot (without mdadm.conf) https://bugs.launchpad.net/bugs/541058 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 652327] Re: mdadm update is scaring me: YOUR SYSTEM IS NOW UNBOOTABLE!
@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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 652327] Re: mdadm update is scaring me: YOUR SYSTEM IS NOW UNBOOTABLE!
@whoop, will you please do the following: 1) copy your mdadm.conf somewhere safe 2) run /usr/share/mdadm/mkconf and see if the definition of md0 is in place. If so please use generate with mkconf to generate a new mdadm.conf. While updating initramfs, the mdadm's initramfs hook expects that the mdadm.conf has *uuid's* instead of /dev/node kind of names. As you can see this is a warning which asks you to verify the array definition, just in case its not present. This is just to prevent the case that your array cannot be auto assembled (which at present it cant be with the current mdadm-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 me: YOUR SYSTEM IS NOW UNBOOTABLE! https://bugs.launchpad.net/bugs/652327 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 603582] Re: Please merge mdadm 3.1.4-1 (main) from Debian stable (main)
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 works. These need wider testing after which they will see their way in the Ubuntu's mdadm package. These patches shall be applied both to 2.7.1 and 3.4.1 soon! As for the delta with respect to Jools work, I am not aware of it at this point. I will sync up with him on irc. Thanks for pointing this out. -- 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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 603582] Re: Please merge mdadm 3.1.2-2 (main) from Debian stable (main)
** 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) https://bugs.launchpad.net/bugs/603582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 603582] Re: 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 of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 603582] Re: Please merge mdadm 3.1.2-2 (main) from Debian stable (main)
** 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 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 603582] Re: Please merge mdadm 3.1.2-2 (main) from Debian stable (main)
** 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) https://bugs.launchpad.net/bugs/603582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 603582] Re: 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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 603582] Re: Please merge mdadm 3.1.2-2 (main) from Debian stable (main)
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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 603582] Re: Please merge mdadm 3.1.4-1 (main) from Debian stable (main)
** 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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 577239] Re: crypted lvm on raid does not boot (lvm device name ... does not begin with /dev/mapper/)
** 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 577239] Re: crypted lvm on raid does not boot (lvm device name ... does not begin with /dev/mapper/)
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 a symbolic link from /dev/by /dev/disk/by-uuid/uuid to /dev/mapper/vol-group. Attaching a cryptsetup patch that fixes this part. Currently Ubuntu's mdadm faces a few problems in autoassembly. However a assembly based on mdadm.conf with appropriate mdadm array definitions in /etc/mdadm/mdadm.conf (both in real root and initramfs) will help assemble the array at boot time. I have kept the mdadm fixes for autoassembly to work at: https://edge.launchpad.net/~csurbhi/+archive/lucid?field.series_filter= (kept in a ppa named lucid) Note that the uuid needs to be updated for the autoassembly to work at boot time. This can be done by 1) installing the test mdadm ppa. 2) Note your uuid by mdadm --detail --scan 3) update-initramfs 4) try autoassembly by rebooting. This will still fail and you will get to an initramfs prompt. At this time, test if your hostname is set appropriately. If it is, then run mdadm --assemble -U uuid. Note if your uuid has changed (it should at this point and correspond to your hostname) 3) try rebooting. Once your uuid has been updated to correspond with your hostname, the autoassembly of the md devices should ideally work. However note that this is a test ppa and yet under testing. Please try at your own risk ;-) and ofcourse let us know if there are any bugs in it if you happen to catch them :-) For now, the attached patch shall take care of the /dev/mapper error message! -- 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
