{"action":"created","issue":{"url":"https://api.github.com/repos/rear/rear/issues/533","labels_url":"https://api.github.com/repos/rear/rear/issues/533/labels{/name}","comments_url":"https://api.github.com/repos/rear/rear/issues/533/comments","events_url":"https://api.github.com/repos/rear/rear/issues/533/events","html_url":"https://github.com/rear/rear/issues/533","id":54907544,"number":533,"title":"rear git201501071534 \"udevadm settle --timeout=20\" hangs endlessly in recovery system for openSUSE 13.2","user":{"login":"jsmeix","id":1788608,"avatar_url":"https://avatars.githubusercontent.com/u/1788608?v=3","gravatar_id":"","url":"https://api.github.com/users/jsmeix","html_url":"https://github.com/jsmeix","followers_url":"https://api.github.com/users/jsmeix/followers","following_url":"https://api.github.com/users/jsmeix/following{/other_user}","gists_url":"https://api.github.com/users/jsmeix/gists{/gist_id}","starred_url":"https://api.github.com/users/jsmeix/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jsmeix/subscriptions","organizations_url":"https://api.github.com/users/jsmeix/orgs","repos_url":"https://api.github.com/users/jsmeix/repos","events_url":"https://api.github.com/users/jsmeix/events{/privacy}","received_events_url":"https://api.github.com/users/jsmeix/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/rear/rear/labels/enhancement","name":"enhancement","color":"02e10c"},{"url":"https://api.github.com/repos/rear/rear/labels/support","name":"support","color":"02d7e1"}],"state":"open","locked":false,"assignee":{"login":"gdha","id":888633,"avatar_url":"https://avatars.githubusercontent.com/u/888633?v=3","gravatar_id":"","url":"https://api.github.com/users/gdha","html_url":"https://github.com/gdha","followers_url":"https://api.github.com/users/gdha/followers","following_url":"https://api.github.com/users/gdha/following{/other_user}","gists_url":"https://api.github.com/users/gdha/gists{/gist_id}","starred_url":"https://api.github.com/users/gdha/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gdha/subscriptions","organizations_url":"https://api.github.com/users/gdha/orgs","repos_url":"https://api.github.com/users/gdha/repos","events_url":"https://api.github.com/users/gdha/events{/privacy}","received_events_url":"https://api.github.com/users/gdha/received_events","type":"User","site_admin":false},"milestone":{"url":"https://api.github.com/repos/rear/rear/milestones/4","labels_url":"https://api.github.com/repos/rear/rear/milestones/4/labels","id":101653,"number":4,"title":"Rear v1.17","description":"Updates which missed the v1.16 release. Bug fixes and some minor new features...","creator":{"login":"dagwieers","id":388198,"avatar_url":"https://avatars.githubusercontent.com/u/388198?v=3","gravatar_id":"","url":"https://api.github.com/users/dagwieers","html_url":"https://github.com/dagwieers","followers_url":"https://api.github.com/users/dagwieers/followers","following_url":"https://api.github.com/users/dagwieers/following{/other_user}","gists_url":"https://api.github.com/users/dagwieers/gists{/gist_id}","starred_url":"https://api.github.com/users/dagwieers/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dagwieers/subscriptions","organizations_url":"https://api.github.com/users/dagwieers/orgs","repos_url":"https://api.github.com/users/dagwieers/repos","events_url":"https://api.github.com/users/dagwieers/events{/privacy}","received_events_url":"https://api.github.com/users/dagwieers/received_events","type":"User","site_admin":false},"open_issues":37,"closed_issues":42,"state":"open","created_at":"2012-03-29T13:41:45Z","updated_at":"2015-01-25T17:09:35Z","due_on":"2015-02-27T23:00:00Z","closed_at":null},"comments":37,"created_at":"2015-01-20T16:48:11Z","updated_at":"2015-01-26T10:30:37Z","closed_at":null,"body":"I am testing rear git201501071534 version on openSUSE 13.2.\r\n\r\nIt basically works but needs manual interventions because\r\n\"rear -d -D recover\" hangs at 'Creating partitions for disk /dev/sda (msdos)' at all the parted steps.\r\n\r\nI have to manually kill each \"/sbin/udevadm settle --timeout=20\" process to enforce it to proceed.\r\n\r\nFor each parted step it hangs with those processes:\r\n<pre>\r\nRESCUE f74:~ # ps aw | grep -A1 parted\r\n 2130 tty1     S+     0:00 parted -s /dev/sda mklabel msdos\r\n 2131 tty1     S+     0:00 /sbin/udevadm settle --timeout=20\r\n\r\nRESCUE f74:~ # kill 2131\r\n\r\nRESCUE f74:~ # ps aw | grep -A1 parted\r\n 2144 tty1     S+     0:00 parted -s /dev/sda mkpart \"primary\" 1048576B 1570766847B\r\n 2145 tty1     S+     0:00 /sbin/udevadm settle --timeout=20\r\n\r\nRESCUE f74:~ # kill 2145\r\n\r\nRESCUE f74:~ # ps aw | grep -A1 parted\r\n 2150 tty1     S+     0:00 parted -s /dev/sda mkpart \"primary\" 1570766848B 12313427967B\r\n 2151 tty1     S+     0:00 /sbin/udevadm settle --timeout=20\r\n\r\nRESCUE f74:~ # kill 2151\r\n\r\nRESCUE f74:~ # ps aw | grep -A1 parted\r\n 2156 tty1     S+     0:00 parted -s /dev/sda mkpart \"primary\" 12313427968B 21474836479B\r\n 2157 tty1     S+     0:00 /sbin/udevadm settle --timeout=20\r\n\r\nRESCUE f74:~ # kill 2157\r\n\r\nRESCUE f74:~ # ps aw | grep -A1 partprobe\r\n 2161 tty1     S+     0:00 partprobe -s /dev/sda\r\n 2162 tty1     S+     0:00 /sbin/udevadm settle --timeout=20\r\n\r\nRESCUE f74:~ # kill 2162\r\n</pre>\r\n"},"comment":{"url":"https://api.github.com/repos/rear/rear/issues/comments/71441012","html_url":"https://github.com/rear/rear/issues/533#issuecomment-71441012","issue_url":"https://api.github.com/repos/rear/rear/issues/533","id":71441012,"user":{"login":"jsmeix","id":1788608,"avatar_url":"https://avatars.githubusercontent.com/u/1788608?v=3","gravatar_id":"","url":"https://api.github.com/users/jsmeix","html_url":"https://github.com/jsmeix","followers_url":"https://api.github.com/users/jsmeix/followers","following_url":"https://api.github.com/users/jsmeix/following{/other_user}","gists_url":"https://api.github.com/users/jsmeix/gists{/gist_id}","starred_url":"https://api.github.com/users/jsmeix/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jsmeix/subscriptions","organizations_url":"https://api.github.com/users/jsmeix/orgs","repos_url":"https://api.github.com/users/jsmeix/repos","events_url":"https://api.github.com/users/jsmeix/events{/privacy}","received_events_url":"https://api.github.com/users/jsmeix/received_events","type":"User","site_admin":false},"created_at":"2015-01-26T10:30:37Z","updated_at":"2015-01-26T10:30:37Z","body":"To all,\r\n\r\nperhaps I fould out the real root cause of the trouble here.\r\n\r\nI asked a colleague who is an expert for the storage setup in the SUSE setup tools YaST and AutoYaST.\r\n\r\nHe told me that the root cause why MD stuff becomes active could be the following:\r\n\r\nWhen recovery is done on a harddisk that was already used before (in particular when recovery is done on the same machine), then parted would re-create same partitions as already have been on the disk.\r\n\r\nWhen a new partition was set up ther are udev rules that run whatever stuff that inspects the new created partition.\r\n\r\nWhen the new created partition is the same as it was before on the disk, the content of the data blocks in that partition is the same as it was before on the disk.\r\n\r\nMD devices and similar stuff like LVM and some others maintain information that is specific for their particular special kind of usage in some kind of \"super blocks\" which are stored in a specific way for each kind of special usage.\r\n\r\nWhen udev runs MD stuff that inspects the new created partition, it may find its specific \"MD super block\" and read from it that thsi partition belongs e.g. to a MD RAID. Accordingly MD tools do \"the right thing\" in this case.\r\n\r\nIf my colleague is right in his assumption, we have a very generic problem to solve here which is:\r\n\r\nBefore parted is run, one must make sure the partition which will be created by parted does no longer contain any data that could mislead lother tools which inspect the partition when it was created.\r\n\r\nMy colleague told me that we have the same problem in AutoYaST (a tool for automated installations via YaST) where usres ofter do an automated re-installation onto the same harddisk.\r\n\r\nI was told that there is the \"wipefs\" tool that is specifically made to wipe those special \"super blocks\".\r\n\r\nPerhaps rear can also use wipefs?\r\n\r\nThe problem is that one would have to wipe those special \"super blocks\" in a partition before parted creates the partition because after parted had created the partition udev would immediatels start the partitioning analyzing tools.\r\n\r\nAll this is currently only FYI it is not yet verified by me.\r\n\r\ntbsky,\r\ncan you re-test on RHEL6 on a new harddisk (e.g. no a new virtual machine) whether or not then MD stuff does still interfere with parted?\r\n"}}