[00:00] <udsbotu> uds-jb-1: This session has ended.
[00:00] <cr3> cheerio folks!
[00:07] <psusi> I believe the current status is that the init scripts time out waiting for the root fs, and then before dropping the user to the initramfs prompt, try to activate the raid array degraded... that only works for the root fs, not other degraded arrays
[00:07] <psusi> instead the degrading should be done plug and play via udev
[00:10] <psusi> the volume holding luks should be identified by udev/blkid as such and decrypted, and then udev/blkid should identify the contents of the luks volume as a raid component
[00:13] <psusi> I would think that if human intervention is required for luks anyhow, that enabling automatic boot to degraded mode would not make sense anyhow
[00:17] <psusi> afaik, blkid identifies a device as a raid component, and that triggers udev to invoke mdadm --incremental, which activates the array if all devices are found already
[00:18] <xnox> https://wiki.ubuntu.com/ReliableRaid
[00:18] <xnox> https://wiki.ubuntu.com/BootDegradedRaid
[00:19] <xnox> psusi, hello 0/ =)
[00:19] <psusi> o/
[00:19]  * psusi beats the icecast server
[00:23] <psusi> the low level kernel disk driver IO error is probably unimportant... the important part is when mdadm notices the error and fails the disk, and when it does that, it normally sends root an email about the event, but ubuntu typically has no mail server installed so that falls into /dev/null
[00:25] <psusi> no, drive registration order is not at all consistent
[00:25] <psusi> that's why we moved to using UUIDs in /etc/fstab
[00:26] <xnox> ok
[00:27] <psusi> that sounds like a bug in udev/blkid
[00:27] <psusi> udev/blkid should identify the partition as a luks container so it won't get assigned a fs UUID and won't be mounted directly without going thorugh mdadm
[00:29] <xnox> ok.
[00:29] <psusi> I wonder... if he was using the whole disk as a raid component instead of a partition, that could trigger it
[00:29] <xnox> the notifications will be handled as part of the 'Degraded Hardware Notifications' spec which i'm driving
[00:29] <psusi> since blkid may identify sda as a raid component, but sda1 still gets identified as a luks volume or fs and accessed without mdadm
[00:30] <xnox> psusi: interesting
[00:30] <psusi> that seems related to an issue I've kind of felt should be changed for a few years now... that being that the kernel partition code should be removed and udev should handle it so it can do things like NOT recognize partitions when the raw disk is part of a raid array
[00:31] <xnox> there were some bugs about 'leftover' metada which doesn't match what was suppose to be assembled correctly
[00:31] <xnox> ok.
[00:32] <psusi> there is scsi enclosure services... if the hardware suppors SES, then there is a /sys way to make a light blink to identify a drive, you just have to map from /dev/sda to the enclosure slot
[00:32] <psusi> iirc, there was a question on askubuntu or unix&linux lately about how to do this with a good answer
[00:32] <psusi> same thing ;)
[00:33] <xnox> I will monitor askubuntu about raid/lvm stuff =)
[00:40] <psusi> bingo!
[00:40] <psusi> http://unix.stackexchange.com/questions/36915/locate-disk-in-sas-enclosure
[00:44] <psusi> could you try to speak more towards the mic please?
[00:50] <psusi> did someone move the mic?  I can't hear anything now
[00:54] <udsbotu> uds-jb-1: 5 minutes left in this session!
[00:55] <udsbotu> uds-jb-1: 4 minutes left in this session!
[00:56] <udsbotu> uds-jb-1: 3 minutes left in this session!
[00:57] <udsbotu> uds-jb-1: 2 minutes left in this session!
[00:58] <udsbotu> uds-jb-1: 1 minute left in this session!
[00:59] <udsbotu> uds-jb-1: This session has ended.
[16:49] <udsbotu> uds-jb-1: 5 minutes left in this session!
[16:51] <udsbotu> uds-jb-1: 4 minutes left in this session!
[16:52] <udsbotu> uds-jb-1: 3 minutes left in this session!
[16:52] <udsbotu> uds-jb-1: 2 minutes left in this session!
[16:53] <udsbotu> uds-jb-1: 1 minute left in this session!
[16:54] <udsbotu> uds-jb-1: This session has ended.
[18:50] <udsbotu> uds-jb-1: 5 minutes left in this session!
[18:51] <udsbotu> uds-jb-1: 4 minutes left in this session!
[18:52] <udsbotu> uds-jb-1: 3 minutes left in this session!
[18:53] <udsbotu> uds-jb-1: 2 minutes left in this session!
[18:54] <udsbotu> uds-jb-1: 1 minute left in this session!
[18:55] <udsbotu> uds-jb-1: This session has ended.
[19:14] <bobweaver> can you turn up the mic I can not hear you
[19:18] <bobweaver> QUESTION: Hello I am upstream dev ,People on debian want too get yell and scream about software and "Yet another program that ubuntu is not sharing" but then when you go to submit things too them. they yell at you make you feel like trash and tell you that you are no-good. the policy is old and out of control How too deal with that ?
[19:25] <bobweaver> Thanks !
[19:32] <bobweaver> quickly is still broken >
[19:32] <bobweaver> ?
[19:36] <carif> QUESTION: what's the "trello board"?
[19:39] <carif> got it, ty
[19:39] <dpm> http://summit.ubuntu.com/uds-q/meeting/20413/community-q-upstream-outreach/
[19:55] <udsbotu> uds-jb-1: 5 minutes left in this session!
[19:56] <udsbotu> uds-jb-1: 4 minutes left in this session!
[19:57] <udsbotu> uds-jb-1: 3 minutes left in this session!
[19:58] <udsbotu> uds-jb-1: 2 minutes left in this session!
[19:59] <udsbotu> uds-jb-1: 1 minute left in this session!
[20:00] <udsbotu> uds-jb-1: This session has ended.