From sundaram at fedoraproject.org Thu Oct 1 23:41:43 2009 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Fri, 02 Oct 2009 05:11:43 +0530 Subject: [fedora-india] F11 connection probs in internet In-Reply-To: <94c1b78f0909270103y356230d3pf5d4a72fc68d8ee8@mail.gmail.com> References: <94c1b78f0909270103y356230d3pf5d4a72fc68d8ee8@mail.gmail.com> Message-ID: <4AC53E37.6030607@fedoraproject.org> On 09/27/2009 01:33 PM, gaurav agrawal wrote: > I istalled fedora 11 with / partition with ext3 filesystem and 500 MB > swap partition. > I have followed the same procedure i have been following for f9 and f10. > when f11 loaded, the palimpsest disk utility shows that you have errors > on disc. > i installed a fresh copy of f11 again but the same problem arises. Palimpsest actually uses smartd which is a hard disk diagnostics program that detects potentially hard disk failures in advance. Simply reinstallation is not to change anything at all. Your hard disk is likely having bad sectors. > > I am unable to configure my internet connection(ppp using ethernet..bsnl > broadband) through system--> administration-->network > The activate/deactivate buttons appears grey. For broadband connections, you should be using NetworkManager instead. Works much better. Rahul From g5_fosslover at yahoo.in Fri Oct 2 13:54:21 2009 From: g5_fosslover at yahoo.in (Gaurav Prabhu) Date: Fri, 2 Oct 2009 19:24:21 +0530 (IST) Subject: [fedora-india] F11 connection probs in internet In-Reply-To: <4AC53E37.6030607@fedoraproject.org> Message-ID: <20643.46649.qm@web95410.mail.in2.yahoo.com> On 09/27/2009 01:33 PM, gaurav agrawal wrote: > I istalled fedora 11 with? / partition with ext3 filesystem and 500 MB > swap partition. > I have followed the same procedure i have been following for f9 and f10. > when f11 loaded, the palimpsest disk utility shows that you have errors > on disc. > i installed a fresh copy of f11 again but the same problem arises. Even Fedora 11 showed by hard-disk to be failing when I booted off from a Live CD but then after installing the error never re-appeared. Might it was a temporary bug but in your case it seems as your hard-disk is really on road of death. > > I am unable to configure my internet connection(ppp using ethernet..bsnl > broadband) through system--> administration-->network > The activate/deactivate buttons appears grey. Regards, Gaurav Prabhu Gaurav Live Layman Linux Connect more, do more and share more with Yahoo! India Mail. Learn more. http://in.overview.mail.yahoo.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From sanjay.ankur at gmail.com Fri Oct 2 16:23:35 2009 From: sanjay.ankur at gmail.com (Ankur Sinha) Date: Fri, 02 Oct 2009 21:53:35 +0530 Subject: [fedora-india] DVD writer troubles Message-ID: <1254500615.2630.27.camel@localhost> Hi, I do realize this isnt the right place for the query, but I really dint know where else to ask. My fedora system cannot burn dvds properly. That is, my laptop burner and the new USB burner I got just today. I'm using "wodim" and it continually wastes dvds. Here is an example: [Ankur at Ankur Fedora-11-i386-DVD]$ wodim -scanbus scsibus4: 4,0,0 400) 'HL-DT-ST' 'DVDRAM GSA-4084N' 'KQ09' Removable CD-ROM 4,1,0 401) * 4,2,0 402) * 4,3,0 403) * 4,4,0 404) * 4,5,0 405) * 4,6,0 406) * 4,7,0 407) * scsibus14: 14,0,0 1400) 'SONY ' 'DVD+-RW DW-D56A ' 'PDS7' Removable CD-ROM 14,1,0 1401) * 14,2,0 1402) * 14,3,0 1403) * 14,4,0 1404) * 14,5,0 1405) * 14,6,0 1406) * 14,7,0 1407) * ------------------------------------------ [Ankur at Ankur Fedora-11-i386-DVD]$ su -c ' nice -n -18 wodim -v -eject dev=14,0,0 Fedora-11-i386-DVD.iso ' Password: wodim: No write mode specified. wodim: Asuming -tao mode. wodim: Future versions of wodim may have different drive dependent defaults. TOC Type: 1 = CD-ROM scsidev: '14,0,0' scsibus: 14 target: 0 lun: 0 WARNING: the deprecated pseudo SCSI syntax found as device specification. Support for that may cease in the future versions of wodim. For now, the device will be mapped to a block device file where possible. Run "wodim --devices" for details. Linux sg driver version: 3.5.27 Wodim version: 1.1.9 SCSI buffer size: 32768 Device type : Removable CD-ROM Version : 0 Response Format: 2 Capabilities : Vendor_info : 'SONY ' Identification : 'DVD+-RW DW-D56A ' Revision : 'PDS7' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Current: 0x0011 (DVD-R sequential recording) Profile: 0x002B (DVD+R/DL) Profile: 0x001B (DVD+R) Profile: 0x001A (DVD+RW) Profile: 0x0014 (DVD-RW sequential recording) Profile: 0x0013 (DVD-RW restricted overwrite) Profile: 0xFE12 () Profile: 0x0011 (DVD-R sequential recording) (current) Profile: 0x0010 (DVD-ROM) Profile: 0x000A (CD-RW) Profile: 0x0009 (CD-R) Profile: 0x0008 (CD-ROM) Using generic SCSI-3/mmc DVD-R(W) driver (mmc_mdvd). Driver flags : SWABAUDIO BURNFREE Supported modes: PACKET SAO Drive buf size : 1563904 = 1527 KB Beginning DMA speed test. Set CDR_NODMATEST environment variable if device communication breaks or freezes immediately after that. FIFO size : 4194304 = 4096 KB Track 01: data 3513 MB Total size: 4034 MB (399:43.26) = 1798745 sectors Lout start: 4034 MB (399:45/20) = 1798745 sectors Current Secsize: 2048 HINT: use dvd+rw-mediainfo from dvd+rw-tools for information extraction. Blocks total: 2298496 Blocks current: 2298496 Blocks remaining: 499751 Speed set to 2770 KB/s Starting to write CD/DVD at speed 2.0 in real unknown mode for single session. Last chance to quit, starting real write in 0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. Performing OPC... Starting new track at sector: 0 Track 01: 1842 of 3513 MB written (fifo 99%) [buf 99%] 3.0x.Errno: 5 (Input/output error), write_g1 scsi sendcmd: retryable error CDB: 2A 00 00 0E 65 D0 00 00 10 00 status: 0x0 (GOOD STATUS) resid: 17408 cmd finished after 42.754s timeout 40s write track data: error after 1932427264 bytes wodim: A write error occured. wodim: Please properly read the error message above. Errno: 5 (Input/output error), test unit ready scsi sendcmd: no error CDB: 00 00 00 00 00 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 04 01 00 00 Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x04 Qual 0x01 (logical unit is in process of becoming ready) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 0.436s timeout 40s Writing time: 542.984s Average write speed 5.0x. Min drive buffer fill was 99% Fixating... Errno: 5 (Input/output error), flush cache scsi sendcmd: no error CDB: 35 00 00 00 00 00 00 00 00 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 04 01 00 00 Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x04 Qual 0x01 (logical unit is in process of becoming ready) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 0.940s timeout 120s Trouble flushing the cache wodim: Cannot fixate disk. Fixating time: 0.940s wodim: fifo had 59101 puts and 58974 gets. wodim: fifo was 0 times empty and 22707 times full, min fill was 72%. I thought it was caused due to a faulty drive. However, as you can see, the new USB drive I got just today gives the same errors. Please advise a course of action. -- regards, Ankur From sameep at tuxwire.com Fri Oct 2 16:24:16 2009 From: sameep at tuxwire.com (Sameep) Date: Fri, 2 Oct 2009 21:54:16 +0530 Subject: [fedora-india] [OT][COM] Fossifieds : FOSS / Linux Classifieds Message-ID: <4B386C4C-5424-4144-955E-76E00A9808E6@tuxwire.com> Fossifieds.com is the first and only premium website dedicated to FOSS & Linux Classifieds . This site was built because there was no website focusing on FOSS and Linux Service providers in India. All FOSS / Linux related classifieds are FREE . Premium classsified spots will be available shortly. Some features you can look forward to are : Automatic SEO Tags for Ads Instant Image Uploading Seller Contact Form Ad Emailing and Printing Ad Editing Seller Dashboard Seller Profile Page Google Map Support Regards, Sameep www.TuxDVDs.com The Best Online Linux Distro Store Latest Distros Ubuntu Ultimate 2.3 Gamer Edition Linux Mint 7 Xfce Zenwalk Linux 6.2 -------------- next part -------------- An HTML attachment was scrubbed... URL: From steve at lonetwin.net Sun Oct 4 12:18:06 2009 From: steve at lonetwin.net (steve) Date: Sun, 04 Oct 2009 17:48:06 +0530 Subject: [fedora-india] DVD writer troubles In-Reply-To: <1254500615.2630.27.camel@localhost> References: <1254500615.2630.27.camel@localhost> Message-ID: <4AC8927E.9090903@lonetwin.net> Hi, On 10/02/2009 09:53 PM, Ankur Sinha wrote: > Hi, > > I do realize this isnt the right place for the query, but I really dint > know where else to ask. > Well, what makes you think this isn't the right place ? :). Of course, you'd get more people trying to help you if you posted on fedora-list[1], so you should consider posting there, but posting here is fine too. > My fedora system cannot burn dvds properly. That is, my laptop burner > and the new USB burner I got just today. I'm using "wodim" and it > continually wastes dvds. > I don't know about wodim, but here are some tips to narrow down the problem: a. Check that the ISO file you are trying to burn isn't corrupt. Quick way would be to mount it: $ mount -o loop -t iso9006 Fedora-11-i386-DVD.iso /mnt $ ls /mnt ...if that works, do a shasum check: http://fedoraproject.org/en/verify b. If the ISO file is ok, try another tool like k3b or brasero (in fact, if I am not mistaken, with an ISO file even a dd should work fine -- i remember doing that a couple of times) c. If writing still fails, I'd suspect the media. Try blank media from a different set /brand -- sometimes one just gets unlucky with bad quality media. d. If all else fails report back here or on fedora-list. HTH, cheers, - steve [1] https://www.redhat.com/mailman/listinfo/fedora-list -- random non tech spiel: http://lonetwin.blogspot.com/ tech randomness: http://lonehacks.blogspot.com/ what i'm stumbling into: http://lonetwin.stumbleupon.com/ From imsumit0103 at in.com Mon Oct 5 06:38:38 2009 From: imsumit0103 at in.com (Sumit Shekhar) Date: Mon, 05 Oct 2009 12:08:38 +0530 Subject: [fedora-india] Error: Cannot retrieve repository metadata Message-ID: <1254724718.580f9aa264f1108da3db844806f3952e@mail.in.com> Dear Sir, i m new to fedora linux.i have downloaded fedora 12 alpha and installed on my laptop.when i tring to update from Internet i m getting fallowing error .kindly do the needful. " [root at localhost ~]# yum install updatesLoaded plugins: refreshpackagekit Error: Cannot retrieve repository metadata (repomd.xml) for repository: InstallMedia. Please verify its path and try again"RegarsSumitDear fedoraindia! Get Yourself a cool, short @in.com Email ID now! -------------- next part -------------- An HTML attachment was scrubbed... URL: From josemanimala at gmail.com Mon Oct 5 06:53:06 2009 From: josemanimala at gmail.com (Jose Mathew Manimala) Date: Mon, 05 Oct 2009 12:23:06 +0530 Subject: [fedora-india] Error: Cannot retrieve repository metadata In-Reply-To: <1254724718.580f9aa264f1108da3db844806f3952e@mail.in.com> References: <1254724718.580f9aa264f1108da3db844806f3952e@mail.in.com> Message-ID: <4AC997D2.7090407@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hello sumit, try these steps out. service yum-updatesd stop ps aux|grep yum # kill off any running yum processes ps aux|grep rpm # kill off any running rpm processes # if necessary, delete the region db's... rm /var/lib/rpm/__*db # then rpm --rebuilddb Regards Jose Mathew Manimala Sumit Shekhar wrote: > Dear Sir, > > i m new to fedora linux.i have downloaded fedora 12 alpha and installed > on my laptop. > > when i tring to update from Internet i m getting fallowing error .kindly > do the needful. > > " [root at localhost ~]# yum install updates > Loaded plugins: refresh-packagekit > Error: Cannot retrieve repository metadata (repomd.xml) for repository: > InstallMedia. Please verify its path and try again" > > Regars > > Sumit > > > Dear *fedora-india!* Get Yourself a cool, short *@in.com* Email ID now! > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Fedora-india mailing list > Fedora-india at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-india -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) iEYEARECAAYFAkrJl9EACgkQ68U/vco3DlJdHACfdXzZI05wMJ2dcLRcWrtcOUWD toEAn3ogrdPXU/0ennneJyqEOkT6tB/8 =JP4Y -----END PGP SIGNATURE----- From steve at lonetwin.net Tue Oct 6 05:14:52 2009 From: steve at lonetwin.net (steve) Date: Tue, 06 Oct 2009 10:44:52 +0530 Subject: [fedora-india] Error: Cannot retrieve repository metadata In-Reply-To: <4AC997D2.7090407@gmail.com> References: <1254724718.580f9aa264f1108da3db844806f3952e@mail.in.com> <4AC997D2.7090407@gmail.com> Message-ID: <4ACAD24C.5020401@lonetwin.net> Hi, On 10/05/2009 12:23 PM, Jose Mathew Manimala wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > [ ...snip... ] > # if necessary, delete the region db's... > > rm /var/lib/rpm/__*db > NO, NO, NO, dear God NO !! This is almost *never* a good idea. This is usually recommended if things go horribly wrong with the rpm DB (which is not even the case here !) If you are not sure about your answers, please at least refrain from giving arbitrary random bad advice ! >> i m new to fedora linux.i have downloaded fedora 12 alpha and installed >> on my laptop. >> >> when i tring to update from Internet i m getting fallowing error .kindly >> do the needful. >> >> " [root at localhost ~]# yum install updates >> Loaded plugins: refresh-packagekit >> Error: Cannot retrieve repository metadata (repomd.xml) for repository: >> InstallMedia. Please verify its path and try again" >> The error message says it all: a. yum cannot retrieve the repository metadata that it needs b. this happened when it was trying to retrieve the metadata from the repository 'InstallMedia' c. it further suggests that you verify the path of the InstallMedia repository and try again. Now, since you are new to Fedora, here is what you can do: a. Try using Fedora 11 instead of Fedora 12 alpha -- the 'alpha' implies that the release is still under development and you should expect things to break and you should know enough about how Fedora works to be able to deal with the breakage. b. If you still want to continue using Fedora 12, disable/edit the InstallMedia repository and also add the fedora online repositories (if they don't exist) to your yum conf. How exactly that is to be done, is left to you (or any others who wish to answer). Explore, play around and ask better questions[1] if you still don't get too far. cheers, - steve [1] http://catb.org/~esr/faqs/smart-questions.html -- random non tech spiel: http://lonetwin.blogspot.com/ tech randomness: http://lonehacks.blogspot.com/ what i'm stumbling into: http://lonetwin.stumbleupon.com/ From josemanimala at gmail.com Tue Oct 6 19:00:29 2009 From: josemanimala at gmail.com (Jose Mathew Manimala) Date: Wed, 07 Oct 2009 00:30:29 +0530 Subject: [fedora-india] Error: Cannot retrieve repository metadata In-Reply-To: <4ACAD24C.5020401@lonetwin.net> References: <1254724718.580f9aa264f1108da3db844806f3952e@mail.in.com> <4AC997D2.7090407@gmail.com> <4ACAD24C.5020401@lonetwin.net> Message-ID: <4ACB93CD.1010405@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Yeah, steves right! i didnt notice the exact error. i shouldnt have sent this email that way. my bad! BTW steve i didnt notice the error correctly. but it did work for me after setting the yum configuration right! steve wrote: > Hi, > > On 10/05/2009 12:23 PM, Jose Mathew Manimala wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> [ ...snip... ] >> # if necessary, delete the region db's... >> >> rm /var/lib/rpm/__*db >> > NO, NO, NO, dear God NO !! This is almost *never* a good idea. This is > usually recommended if things go horribly wrong with the rpm DB (which > is not even the case here !) > > If you are not sure about your answers, please at least refrain from > giving arbitrary random bad advice ! > > >>> i m new to fedora linux.i have downloaded fedora 12 alpha and installed >>> on my laptop. >>> >>> when i tring to update from Internet i m getting fallowing error >>> .kindly >>> do the needful. >>> >>> " [root at localhost ~]# yum install updates >>> Loaded plugins: refresh-packagekit >>> Error: Cannot retrieve repository metadata (repomd.xml) for repository: >>> InstallMedia. Please verify its path and try again" >>> > > The error message says it all: > a. yum cannot retrieve the repository metadata that it needs > b. this happened when it was trying to retrieve the metadata from the > repository 'InstallMedia' > c. it further suggests that you verify the path of the InstallMedia > repository and try again. > > Now, since you are new to Fedora, here is what you can do: > > a. Try using Fedora 11 instead of Fedora 12 alpha -- the 'alpha' implies > that the release is still under development and you should expect things > to break and you should know enough about how Fedora works to be able to > deal with the breakage. > > b. If you still want to continue using Fedora 12, disable/edit the > InstallMedia repository and also add the fedora online repositories (if > they don't exist) to your yum conf. How exactly that is to be done, is > left to you (or any others who wish to answer). Explore, play around and > ask better questions[1] if you still don't get too far. > > cheers, > - steve > > [1] http://catb.org/~esr/faqs/smart-questions.html > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) iEYEARECAAYFAkrLk80ACgkQ68U/vco3DlLKpgCeNg9jOYCeZgUlVuV14US4MaqP YLEAnjVBmefIiXItBlbWD0yxA7wGRCJ7 =dPdM -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: 0xCA370E52.asc Type: application/pgp-keys Size: 1733 bytes Desc: not available URL: From sankarshan at fedoraproject.org Fri Oct 9 03:57:54 2009 From: sankarshan at fedoraproject.org (sankarshan) Date: Fri, 9 Oct 2009 09:27:54 +0530 Subject: [fedora-india] Media, and other requests in the light of holidays coming up Message-ID: <35586fc00910082057n49c58b82o20561372098698d9@mail.gmail.com> Hi, Aside from the well known holidays that are coming up, Maharashtra has elections (and, hence holiday) as well. This would mean that processing the tickets/requests via the trac would be impacted. Please bear with us. For all requests and the like, please read before opening a new ticket. Do also note that we are nearly out of DVDs for 32 bit systems. However we do have some LiveCDs which we can ship. /sankarshan -- sankarshan mukhopadhyay From parshwa23 at gmail.com Fri Oct 9 11:22:46 2009 From: parshwa23 at gmail.com (Parshwa Murdia) Date: Fri, 9 Oct 2009 16:52:46 +0530 Subject: [fedora-india] I want to ask something Message-ID: <7856eaf20910090422m645eb85dna0383013013f8f6f@mail.gmail.com> Hi all, Please anyone tell me what I do?? What happened is that I first installed Windows XP in 60 GB out of 160 GB Harddisk. After that, in the remaining space I installed Fedora Core 11 from the CD (which I burned as image from .iso). After this suddenly I am not able to get either the Fedora or the Windows. So what to do? Please tell me. Here is the error message which is coming whcih I am not able to understand, please explain me. Here is this: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ anaconda 11.5.0.59-1.fc11 exception report Traceback (most recent call first): File "/usr/lib/anaconda/storage/devicelibs/lvm.py", line 357, in lvcreate raise LVMError("lvcreate failed for %s/%s" % (vg_name, lv_name)) File "/usr/lib/anaconda/storage/devices.py", line 2137, in create lvm.lvcreate(self.vg.name, self._name, self.size) File "/usr/lib/anaconda/storage/deviceaction.py", line 203, in execute self.device.create(intf=intf) File "/usr/lib/anaconda/storage/devicetree.py", line 671, in processActions action.execute(intf=self.intf) File "/usr/lib/anaconda/storage/__init__.py", line 238, in doIt self.devicetree.processActions() File "/usr/lib/anaconda/packages.py", line 117, in turnOnFilesystems anaconda.id.storage.doIt() LVMError: lvcreate failed for vg_parshwahost/lv_root Local variables in innermost frame: size: 150408 args: ['lvcreate', '-L', '150408m', '-n', 'lv_root', 'vg_parshwahost'] lv_name: lv_root vg_name: vg_parshwahost rc: 5 Anaconda instance, containing members: rescue_mount: True reIPLMessage: None intf: InstallInterface instance, containing members: intf.icw: InstallControlWindow instance, containing members: intf.icw.handle: 1013 intf.icw.currentWindow: PartitionWindow instance, containing members: intf.icw.currentWindow.checkmark_pixbuf: intf.icw.currentWindow.intf: Already dumped intf.icw.currentWindow.diskStripeGraph: DiskStripeGraph instance, containing members: intf.icw.currentWindow.diskStripeGraph.canvas: intf.icw.currentWindow.diskStripeGraph.textlabels: [] intf.icw.currentWindow.diskStripeGraph.tree: intf.icw.currentWindow.diskStripeGraph.editCB: > intf.icw.currentWindow.diskStripeGraph.next_ypos: 0.0 intf.icw.currentWindow.diskStripeGraph.diskStripes: [] intf.icw.currentWindow.show_uneditable: 1 intf.icw.currentWindow.lock_pixbuf: intf.icw.currentWindow.storage: intf.icw.currentWindow.tree: intf.icw.currentWindow.toggleViewButton: intf.icw.currentWindow.anaconda: Already dumped intf.icw.currentWindow.ics: InstallControlState instance, containing members: intf.icw.currentWindow.ics.prevEnabled: True intf.icw.currentWindow.ics.cw: Already dumped intf.icw.currentWindow.ics.nextEnabled: True intf.icw.currentWindow.ics.grabNext: True intf.icw.currentWindow.ics.title: Partitioning intf.icw.currentWindow.treeViewSelection: intf.icw.currentWindow.treeView: intf.icw.mainxml: intf.icw.window: intf.icw.installFrame: intf.icw.anaconda: Already dumped intf.icw.reloadRcQueued: 0 intf.runres: 800x600 intf.anaconda: Already dumped rescue: False updateSrc: None mediaDevice: None methodstr: livecd:///dev/mapper/live-osimg-min dispatch: rootPath: /mnt/sysimage platform: canReIPL: False xdriver: None isKickstart: False stage2: None id: InstallData instance, containing members: id.firewall: Firewall instance, containing members: id.firewall.portlist: [] id.firewall.servicelist: [] id.firewall.trustdevs: [] id.firewall.enabled: 1 id.anaconda: Already dumped id.upgradeRoot: None id.keyboard: Keyboard instance, containing members: id.keyboard.info: {'LAYOUT': us, 'KEYBOARDTYPE': pc, 'VARIANT': , 'KEYTABLE': us, 'MODEL': pc105+inet, 'OPTIONS': } id.keyboard.type: PC id.keyboard._mods: KeyboardModels instance, containing members: id.keyboard.beenset: 1 id.timezone: Timezone instance, containing members: id.timezone.utc: True id.timezone.tz: Asia/Kolkata id.backend: LiveCDCopyBackend instance, containing members: id.backend.instPath: /mnt/sysimage id.backend.skipFormatRoot: True id.backend.instLog: None id.backend.supportsUpgrades: False id.backend._loopbackFile: None id.backend.rootFsType: ext4 id.backend.osimg: //dev/mapper/live-osimg-min id.backend.supportsPackageSelection: False id.upgrade: None id.monitor: None id.storage: id.desktop: Desktop instance, containing members: id.desktop.info: {} id.desktop.runlevel: 3 id.rootParts: None id.x_already_set: 1 id.firstboot: 0 id.users: None id.displayMode: g id.auth: --enableshadow --passalgo=sha512 --enablefingerprint id.ksdata: None id.bootloader: x86BootloaderInfo instance, containing members: id.bootloader._configdir: /boot/grub id.bootloader.doUpgradeOnly: 0 id.bootloader.above1024: 0 id.bootloader.defaultDevice: None id.bootloader.pure: None id.bootloader.storage: id.bootloader.serialOptions: None id.bootloader.args: KernelArguments instance, containing members: id.bootloader.kernelLocation: /boot/ id.bootloader.timeout: None id.bootloader._configname: grub.conf id.bootloader.device: None id.bootloader.kickstart: 0 id.bootloader.serialDevice: None id.bootloader.useGrubVal: 1 id.bootloader._drivelist: [sda] id.bootloader.images: BootImages instance, containing members: id.bootloader.images.default: None id.bootloader.images.images: {} id.bootloader.serial: 0 id.bootloader.password: None id.bootloader.forceLBA32: 0 id.extraModules: [] id.network: Network instance, containing members: id.network.netdevices: {'eth0': DEVICE=eth0 HWADDR=00:E0:4C:19:26:95 } id.network.ksdevice: None id.network.overrideDHCPhostname: False id.network.hostname: parshwahost.acldomain id.network.domains: [] id.instClass: id.isHeadless: 0 id.videocard: None id.instLanguage: Language instance, containing members: id.instLanguage.targetLang: None id.instLanguage.default: en_US.UTF-8 id.instLanguage.displayMode: g id.instLanguage.current: en_US.UTF-8 id.security: Security instance, containing members: id.security.selinux: 1 id.upgradeSwapInfo: None dir: 1 backend: Already dumped /tmp/anaconda.log: 16:12:37 INFO : using only installclass _Fedora 16:12:37 INFO : anaconda called with cmdline = ['/usr/sbin/anaconda', '--liveinst', '--method=livecd:///dev/mapper/live-osimg-min', '--lang', 'en_US.UTF-8'] 16:12:37 INFO : Display mode = g 16:12:37 INFO : Starting graphical installation... 16:12:37 INFO : Detected 1008M of memory 16:12:37 INFO : Swap attempt of 1008M to 2016M 16:12:37 WARNING : step installtype does not exist 16:12:37 WARNING : step confirminstall does not exist 16:12:37 WARNING : step complete does not exist 16:12:37 INFO : moving (1) to step welcome 16:12:39 INFO : moving (1) to step keyboard 16:12:40 INFO : moving (1) to step storageinit 16:12:40 INFO : no /tmp/fcpconfig; not configuring zfcp 16:12:43 DEBUG : DeviceTree.addUdevDevice: name: sda ; 16:12:43 DEBUG : DeviceTree.addUdevDiskDevice: name: sda ; 16:12:43 DEBUG : DiskDevice._setFormat: sda ; current: None ; type: None ; 16:12:49 DEBUG : DeviceTree.handleUdevDeviceFormat: name: sda ; 16:12:49 DEBUG : DeviceTree.addUdevDevice: name: sda1 ; 16:12:49 DEBUG : DeviceTree.addUdevPartitionDevice: name: sda1 ; 16:12:49 DEBUG : DiskDevice.addChild: kids: 0 ; name: sda ; 16:12:49 DEBUG : PartitionDevice._setFormat: sda1 ; 16:12:49 DEBUG : PartitionDevice._setFormat: sda1 ; current: None ; type: None ; 16:12:49 DEBUG : PartitionDevice.probe: sda1 ; exists: True ; 16:12:49 DEBUG : PartitionDevice._computeResize: sda1 ; status: True ; 16:12:49 DEBUG : PartitionDevice.getFlag: path: /dev/sda1 ; flag: 1 ; part: parted.Partition instance -- disk: fileSystem: number: 1 path: /dev/sda1 type: 0 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94a7efc> ; 16:12:49 DEBUG : PartitionDevice.flagAvailable: path: /dev/sda1 ; flag: 1 ; part: parted.Partition instance -- disk: fileSystem: number: 1 path: /dev/sda1 type: 0 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94a7efc> ; 16:12:49 DEBUG : PartitionDevice.getFlag: path: /dev/sda1 ; flag: 10 ; part: parted.Partition instance -- disk: fileSystem: number: 1 path: /dev/sda1 type: 0 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94a7efc> ; 16:12:49 DEBUG : PartitionDevice.flagAvailable: path: /dev/sda1 ; flag: 10 ; part: parted.Partition instance -- disk: fileSystem: number: 1 path: /dev/sda1 type: 0 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94a7efc> ; 16:12:49 DEBUG : DeviceTree.handleUdevDeviceFormat: name: sda1 ; 16:12:49 DEBUG : Ext3FS.supported: supported: True ; 16:12:49 DEBUG : PartitionDevice._setFormat: sda1 ; 16:12:49 DEBUG : PartitionDevice._setFormat: sda1 ; current: None ; type: ext3 ; 16:12:49 DEBUG : DeviceTree.addUdevDevice: name: sda2 ; 16:12:49 DEBUG : DeviceTree.addUdevPartitionDevice: name: sda2 ; 16:12:49 DEBUG : DiskDevice.addChild: kids: 1 ; name: sda ; 16:12:49 DEBUG : PartitionDevice._setFormat: sda2 ; 16:12:49 DEBUG : PartitionDevice._setFormat: sda2 ; current: None ; type: None ; 16:12:49 DEBUG : PartitionDevice.probe: sda2 ; exists: True ; 16:12:49 DEBUG : PartitionDevice._computeResize: sda2 ; status: True ; 16:12:49 DEBUG : PartitionDevice.getFlag: path: /dev/sda2 ; flag: 1 ; part: parted.Partition instance -- disk: fileSystem: None number: 2 path: /dev/sda2 type: 0 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94a7e9c> ; 16:12:49 DEBUG : PartitionDevice.flagAvailable: path: /dev/sda2 ; flag: 1 ; part: parted.Partition instance -- disk: fileSystem: None number: 2 path: /dev/sda2 type: 0 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94a7e9c> ; 16:12:49 DEBUG : PartitionDevice.getFlag: path: /dev/sda2 ; flag: 10 ; part: parted.Partition instance -- disk: fileSystem: None number: 2 path: /dev/sda2 type: 0 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94a7e9c> ; 16:12:49 DEBUG : PartitionDevice.flagAvailable: path: /dev/sda2 ; flag: 10 ; part: parted.Partition instance -- disk: fileSystem: None number: 2 path: /dev/sda2 type: 0 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94a7e9c> ; 16:12:49 DEBUG : DeviceTree.handleUdevDeviceFormat: name: sda2 ; 16:12:49 DEBUG : DeviceTree.addUdevDevice: name: sda3 ; 16:12:49 DEBUG : DeviceTree.addUdevPartitionDevice: name: sda3 ; 16:12:49 DEBUG : DiskDevice.addChild: kids: 2 ; name: sda ; 16:12:49 DEBUG : PartitionDevice._setFormat: sda3 ; 16:12:49 DEBUG : PartitionDevice._setFormat: sda3 ; current: None ; type: None ; 16:12:49 DEBUG : PartitionDevice.probe: sda3 ; exists: True ; 16:12:49 DEBUG : PartitionDevice._computeResize: sda3 ; status: True ; 16:12:49 DEBUG : PartitionDevice.getFlag: path: /dev/sda3 ; flag: 1 ; part: parted.Partition instance -- disk: fileSystem: None number: 3 path: /dev/sda3 type: 0 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94a7e6c> ; 16:12:49 DEBUG : PartitionDevice.flagAvailable: path: /dev/sda3 ; flag: 1 ; part: parted.Partition instance -- disk: fileSystem: None number: 3 path: /dev/sda3 type: 0 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94a7e6c> ; 16:12:49 DEBUG : PartitionDevice.getFlag: path: /dev/sda3 ; flag: 10 ; part: parted.Partition instance -- disk: fileSystem: None number: 3 path: /dev/sda3 type: 0 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94a7e6c> ; 16:12:49 DEBUG : PartitionDevice.flagAvailable: path: /dev/sda3 ; flag: 10 ; part: parted.Partition instance -- disk: fileSystem: None number: 3 path: /dev/sda3 type: 0 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94a7e6c> ; 16:12:49 DEBUG : DeviceTree.handleUdevDeviceFormat: name: sda3 ; 16:12:49 DEBUG : LVMPhysicalVolume.__init__: device: /dev/sda3 ; peStart: 0.1875 ; uuid: h6NBjv-XRr6-1fK5-4UC3-ymUf-kHA2-7BnKEl ; exists: True ; label: None ; 16:12:49 DEBUG : PartitionDevice._setFormat: sda3 ; 16:12:49 DEBUG : PartitionDevice._setFormat: sda3 ; current: None ; type: lvmpv ; 16:12:49 DEBUG : DeviceTree.handleUdevLVMPVFormat: type: lvmpv ; name: sda3 ; 16:12:49 DEBUG : DeviceTree.addUdevDevice: name: sda4 ; 16:12:49 DEBUG : DeviceTree.addUdevPartitionDevice: name: sda4 ; 16:12:49 DEBUG : DiskDevice.addChild: kids: 3 ; name: sda ; 16:12:49 DEBUG : PartitionDevice._setFormat: sda4 ; 16:12:49 DEBUG : PartitionDevice._setFormat: sda4 ; current: None ; type: None ; 16:12:49 DEBUG : PartitionDevice.probe: sda4 ; exists: True ; 16:12:49 DEBUG : PartitionDevice._computeResize: sda4 ; status: True ; 16:12:49 DEBUG : PartitionDevice.getFlag: path: /dev/sda4 ; flag: 1 ; part: parted.Partition instance -- disk: fileSystem: None number: 4 path: /dev/sda4 type: 2 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94a7f8c> ; 16:12:49 DEBUG : PartitionDevice.flagAvailable: path: /dev/sda4 ; flag: 1 ; part: parted.Partition instance -- disk: fileSystem: None number: 4 path: /dev/sda4 type: 2 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94a7f8c> ; 16:12:49 DEBUG : PartitionDevice.getFlag: path: /dev/sda4 ; flag: 10 ; part: parted.Partition instance -- disk: fileSystem: None number: 4 path: /dev/sda4 type: 2 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94a7f8c> ; 16:12:49 DEBUG : PartitionDevice.flagAvailable: path: /dev/sda4 ; flag: 10 ; part: parted.Partition instance -- disk: fileSystem: None number: 4 path: /dev/sda4 type: 2 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94a7f8c> ; 16:12:49 DEBUG : DeviceTree.handleUdevDeviceFormat: name: sda4 ; 16:12:49 DEBUG : DeviceTree.addUdevDevice: name: sda5 ; 16:12:49 DEBUG : DeviceTree.addUdevPartitionDevice: name: sda5 ; 16:12:49 DEBUG : DiskDevice.addChild: kids: 4 ; name: sda ; 16:12:49 DEBUG : PartitionDevice._setFormat: sda5 ; 16:12:49 DEBUG : PartitionDevice._setFormat: sda5 ; current: None ; type: None ; 16:12:49 DEBUG : PartitionDevice.probe: sda5 ; exists: True ; 16:12:49 DEBUG : PartitionDevice._computeResize: sda5 ; status: True ; 16:12:49 DEBUG : PartitionDevice.getFlag: path: /dev/sda5 ; flag: 1 ; part: parted.Partition instance -- disk: fileSystem: number: 5 path: /dev/sda5 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94a7f2c> ; 16:12:49 DEBUG : PartitionDevice.flagAvailable: path: /dev/sda5 ; flag: 1 ; part: parted.Partition instance -- disk: fileSystem: number: 5 path: /dev/sda5 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94a7f2c> ; 16:12:49 DEBUG : PartitionDevice.getFlag: path: /dev/sda5 ; flag: 10 ; part: parted.Partition instance -- disk: fileSystem: number: 5 path: /dev/sda5 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94a7f2c> ; 16:12:49 DEBUG : PartitionDevice.flagAvailable: path: /dev/sda5 ; flag: 10 ; part: parted.Partition instance -- disk: fileSystem: number: 5 path: /dev/sda5 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94a7f2c> ; 16:12:49 DEBUG : DeviceTree.handleUdevDeviceFormat: name: sda5 ; 16:12:49 DEBUG : SwapSpace.__init__: device: /dev/sda5 ; uuid: 18c20391-3fee-45ae-af9e-5bb724fa206c ; exists: True ; label: None ; 16:12:49 DEBUG : PartitionDevice._setFormat: sda5 ; 16:12:49 DEBUG : PartitionDevice._setFormat: sda5 ; current: None ; type: swap ; 16:12:49 DEBUG : DeviceTree.addUdevDevice: name: sda6 ; 16:12:49 DEBUG : DeviceTree.addUdevPartitionDevice: name: sda6 ; 16:12:49 DEBUG : DiskDevice.addChild: kids: 5 ; name: sda ; 16:12:49 DEBUG : PartitionDevice._setFormat: sda6 ; 16:12:49 DEBUG : PartitionDevice._setFormat: sda6 ; current: None ; type: None ; 16:12:49 DEBUG : PartitionDevice.probe: sda6 ; exists: True ; 16:12:49 DEBUG : PartitionDevice._computeResize: sda6 ; status: True ; 16:12:49 DEBUG : PartitionDevice.getFlag: path: /dev/sda6 ; flag: 1 ; part: parted.Partition instance -- disk: fileSystem: number: 6 path: /dev/sda6 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94a7fbc> ; 16:12:49 DEBUG : PartitionDevice.flagAvailable: path: /dev/sda6 ; flag: 1 ; part: parted.Partition instance -- disk: fileSystem: number: 6 path: /dev/sda6 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94a7fbc> ; 16:12:49 DEBUG : PartitionDevice.getFlag: path: /dev/sda6 ; flag: 10 ; part: parted.Partition instance -- disk: fileSystem: number: 6 path: /dev/sda6 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94a7fbc> ; 16:12:49 DEBUG : PartitionDevice.flagAvailable: path: /dev/sda6 ; flag: 10 ; part: parted.Partition instance -- disk: fileSystem: number: 6 path: /dev/sda6 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94a7fbc> ; 16:12:49 DEBUG : DeviceTree.handleUdevDeviceFormat: name: sda6 ; 16:12:49 DEBUG : Ext4FS.supported: supported: True ; 16:12:49 DEBUG : PartitionDevice._setFormat: sda6 ; 16:12:49 DEBUG : PartitionDevice._setFormat: sda6 ; current: None ; type: ext4 ; 16:12:49 DEBUG : DeviceTree.addUdevDevice: name: sda7 ; 16:12:49 DEBUG : DeviceTree.addUdevPartitionDevice: name: sda7 ; 16:12:49 DEBUG : DiskDevice.addChild: kids: 6 ; name: sda ; 16:12:49 DEBUG : PartitionDevice._setFormat: sda7 ; 16:12:49 DEBUG : PartitionDevice._setFormat: sda7 ; current: None ; type: None ; 16:12:49 DEBUG : PartitionDevice.probe: sda7 ; exists: True ; 16:12:49 DEBUG : PartitionDevice._computeResize: sda7 ; status: True ; 16:12:49 DEBUG : PartitionDevice.getFlag: path: /dev/sda7 ; flag: 1 ; part: parted.Partition instance -- disk: fileSystem: number: 7 path: /dev/sda7 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94b202c> ; 16:12:49 DEBUG : PartitionDevice.flagAvailable: path: /dev/sda7 ; flag: 1 ; part: parted.Partition instance -- disk: fileSystem: number: 7 path: /dev/sda7 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94b202c> ; 16:12:49 DEBUG : PartitionDevice.getFlag: path: /dev/sda7 ; flag: 10 ; part: parted.Partition instance -- disk: fileSystem: number: 7 path: /dev/sda7 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94b202c> ; 16:12:49 DEBUG : PartitionDevice.flagAvailable: path: /dev/sda7 ; flag: 10 ; part: parted.Partition instance -- disk: fileSystem: number: 7 path: /dev/sda7 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94b202c> ; 16:12:49 DEBUG : DeviceTree.handleUdevDeviceFormat: name: sda7 ; 16:12:50 DEBUG : Ext4FS.supported: supported: True ; 16:12:50 DEBUG : PartitionDevice._setFormat: sda7 ; 16:12:50 DEBUG : PartitionDevice._setFormat: sda7 ; current: None ; type: ext4 ; 16:12:50 DEBUG : DeviceTree.addUdevDevice: name: sda8 ; 16:12:50 DEBUG : DeviceTree.addUdevPartitionDevice: name: sda8 ; 16:12:50 DEBUG : DiskDevice.addChild: kids: 7 ; name: sda ; 16:12:50 DEBUG : PartitionDevice._setFormat: sda8 ; 16:12:50 DEBUG : PartitionDevice._setFormat: sda8 ; current: None ; type: None ; 16:12:50 DEBUG : PartitionDevice.probe: sda8 ; exists: True ; 16:12:50 DEBUG : PartitionDevice._computeResize: sda8 ; status: True ; 16:12:50 DEBUG : PartitionDevice.getFlag: path: /dev/sda8 ; flag: 1 ; part: parted.Partition instance -- disk: fileSystem: number: 8 path: /dev/sda8 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94b205c> ; 16:12:50 DEBUG : PartitionDevice.flagAvailable: path: /dev/sda8 ; flag: 1 ; part: parted.Partition instance -- disk: fileSystem: number: 8 path: /dev/sda8 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94b205c> ; 16:12:50 DEBUG : PartitionDevice.getFlag: path: /dev/sda8 ; flag: 10 ; part: parted.Partition instance -- disk: fileSystem: number: 8 path: /dev/sda8 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94b205c> ; 16:12:50 DEBUG : PartitionDevice.flagAvailable: path: /dev/sda8 ; flag: 10 ; part: parted.Partition instance -- disk: fileSystem: number: 8 path: /dev/sda8 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94b205c> ; 16:12:50 DEBUG : DeviceTree.handleUdevDeviceFormat: name: sda8 ; 16:12:50 DEBUG : Ext4FS.supported: supported: True ; 16:12:50 DEBUG : PartitionDevice._setFormat: sda8 ; 16:12:50 DEBUG : PartitionDevice._setFormat: sda8 ; current: None ; type: ext4 ; 16:12:50 DEBUG : DeviceTree.addUdevDevice: name: sda9 ; 16:12:50 DEBUG : DeviceTree.addUdevPartitionDevice: name: sda9 ; 16:12:50 DEBUG : DiskDevice.addChild: kids: 8 ; name: sda ; 16:12:50 DEBUG : PartitionDevice._setFormat: sda9 ; 16:12:50 DEBUG : PartitionDevice._setFormat: sda9 ; current: None ; type: None ; 16:12:50 DEBUG : PartitionDevice.probe: sda9 ; exists: True ; 16:12:50 DEBUG : PartitionDevice._computeResize: sda9 ; status: True ; 16:12:50 DEBUG : PartitionDevice.getFlag: path: /dev/sda9 ; flag: 1 ; part: parted.Partition instance -- disk: fileSystem: None number: 9 path: /dev/sda9 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94b208c> ; 16:12:50 DEBUG : PartitionDevice.flagAvailable: path: /dev/sda9 ; flag: 1 ; part: parted.Partition instance -- disk: fileSystem: None number: 9 path: /dev/sda9 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94b208c> ; 16:12:50 DEBUG : PartitionDevice.getFlag: path: /dev/sda9 ; flag: 10 ; part: parted.Partition instance -- disk: fileSystem: None number: 9 path: /dev/sda9 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94b208c> ; 16:12:50 DEBUG : PartitionDevice.flagAvailable: path: /dev/sda9 ; flag: 10 ; part: parted.Partition instance -- disk: fileSystem: None number: 9 path: /dev/sda9 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94b208c> ; 16:12:50 DEBUG : DeviceTree.handleUdevDeviceFormat: name: sda9 ; 16:12:50 DEBUG : DeviceTree.addUdevDevice: name: sda10 ; 16:12:50 DEBUG : DeviceTree.addUdevPartitionDevice: name: sda10 ; 16:12:50 DEBUG : DiskDevice.addChild: kids: 9 ; name: sda ; 16:12:50 DEBUG : PartitionDevice._setFormat: sda10 ; 16:12:50 DEBUG : PartitionDevice._setFormat: sda10 ; current: None ; type: None ; 16:12:50 DEBUG : PartitionDevice.probe: sda10 ; exists: True ; 16:12:50 DEBUG : PartitionDevice._computeResize: sda10 ; status: True ; 16:12:50 DEBUG : PartitionDevice.getFlag: path: /dev/sda10 ; flag: 1 ; part: parted.Partition instance -- disk: fileSystem: number: 10 path: /dev/sda10 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94b20bc> ; 16:12:50 DEBUG : PartitionDevice.flagAvailable: path: /dev/sda10 ; flag: 1 ; part: parted.Partition instance -- disk: fileSystem: number: 10 path: /dev/sda10 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94b20bc> ; 16:12:50 DEBUG : PartitionDevice.getFlag: path: /dev/sda10 ; flag: 10 ; part: parted.Partition instance -- disk: fileSystem: number: 10 path: /dev/sda10 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94b20bc> ; 16:12:50 DEBUG : PartitionDevice.flagAvailable: path: /dev/sda10 ; flag: 10 ; part: parted.Partition instance -- disk: fileSystem: number: 10 path: /dev/sda10 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94b20bc> ; 16:12:50 DEBUG : DeviceTree.handleUdevDeviceFormat: name: sda10 ; 16:12:50 DEBUG : Ext3FS.supported: supported: True ; 16:12:50 DEBUG : PartitionDevice._setFormat: sda10 ; 16:12:50 DEBUG : PartitionDevice._setFormat: sda10 ; current: None ; type: ext3 ; 16:12:50 DEBUG : DeviceTree.addUdevDevice: name: sda11 ; 16:12:50 DEBUG : DeviceTree.addUdevPartitionDevice: name: sda11 ; 16:12:50 DEBUG : DiskDevice.addChild: kids: 10 ; name: sda ; 16:12:50 DEBUG : PartitionDevice._setFormat: sda11 ; 16:12:50 DEBUG : PartitionDevice._setFormat: sda11 ; current: None ; type: None ; 16:12:50 DEBUG : PartitionDevice.probe: sda11 ; exists: True ; 16:12:50 DEBUG : PartitionDevice._computeResize: sda11 ; status: True ; 16:12:50 DEBUG : PartitionDevice.getFlag: path: /dev/sda11 ; flag: 1 ; part: parted.Partition instance -- disk: fileSystem: None number: 11 path: /dev/sda11 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94b20ec> ; 16:12:50 DEBUG : PartitionDevice.flagAvailable: path: /dev/sda11 ; flag: 1 ; part: parted.Partition instance -- disk: fileSystem: None number: 11 path: /dev/sda11 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94b20ec> ; 16:12:50 DEBUG : PartitionDevice.getFlag: path: /dev/sda11 ; flag: 10 ; part: parted.Partition instance -- disk: fileSystem: None number: 11 path: /dev/sda11 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94b20ec> ; 16:12:50 DEBUG : PartitionDevice.flagAvailable: path: /dev/sda11 ; flag: 10 ; part: parted.Partition instance -- disk: fileSystem: None number: 11 path: /dev/sda11 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94b20ec> ; 16:12:50 DEBUG : DeviceTree.handleUdevDeviceFormat: name: sda11 ; 16:12:50 DEBUG : LVMPhysicalVolume.__init__: vgName: VolGroup ; uuid: 6OVn42-iGEo-d0qW-V86L-7b4B-2qsv-shCcjK ; exists: True ; vgUuid: 1SLacE-6k11-Q6BT-rfKJ-vo7J-OOW8-Xz2ZGh ; label: None ; peStart: 0.1875 ; device: /dev/sda11 ; 16:12:50 DEBUG : PartitionDevice._setFormat: sda11 ; 16:12:50 DEBUG : PartitionDevice._setFormat: sda11 ; current: None ; type: lvmpv ; 16:12:50 DEBUG : DeviceTree.handleUdevLVMPVFormat: type: lvmpv ; name: sda11 ; 16:12:50 DEBUG : PartitionDevice.addChild: kids: 0 ; name: sda11 ; 16:12:50 DEBUG : LVMVolumeGroupDevice._setFormat: VolGroup ; current: None ; type: None ; 16:12:50 DEBUG : LVMVolumeGroupDevice.addChild: kids: 0 ; name: VolGroup ; 16:12:50 DEBUG : LVMLogicalVolumeDevice._setFormat: VolGroup-lv_root ; current: None ; type: None ; 16:12:50 DEBUG : LVMLogicalVolumeDevice.setup: VolGroup-lv_root ; status: False ; 16:12:50 DEBUG : LVMVolumeGroupDevice.setup: VolGroup ; status: True ; 16:12:51 DEBUG : DeviceTree.addUdevDevice: name: live-rw ; 16:12:51 DEBUG : DeviceTree.addUdevDMDevice: name: live-rw ; 16:12:51 DEBUG : LVMLogicalVolumeDevice.getDMNode: VolGroup-lv_root ; status: True ; 16:12:51 DEBUG : LVMVolumeGroupDevice.getDMNode: VolGroup ; status: True ; 16:12:51 DEBUG : DeviceTree.addUdevDevice: name: loop3 ; 16:12:51 DEBUG : DeviceTree.handleUdevDeviceFormat: name: None ; 16:12:51 DEBUG : DeviceTree.addUdevDevice: name: live-osimg-min ; 16:12:51 DEBUG : DeviceTree.addUdevDMDevice: name: live-osimg-min ; 16:12:51 DEBUG : LVMLogicalVolumeDevice.getDMNode: VolGroup-lv_root ; status: True ; 16:12:51 DEBUG : LVMVolumeGroupDevice.getDMNode: VolGroup ; status: True ; 16:12:51 DEBUG : DeviceTree.addUdevDevice: name: loop3 ; 16:12:51 DEBUG : DeviceTree.handleUdevDeviceFormat: name: None ; 16:12:53 DEBUG : DeviceTree.addUdevDevice: name: VolGroup-lv_root ; 16:12:53 DEBUG : DeviceTree.handleUdevDeviceFormat: name: VolGroup-lv_root ; 16:12:53 DEBUG : Ext4FS.supported: supported: True ; 16:12:53 DEBUG : LVMLogicalVolumeDevice._setFormat: VolGroup-lv_root ; current: None ; type: ext4 ; 16:12:53 DEBUG : PartitionDevice.teardown: sda1 ; status: True ; 16:12:53 DEBUG : DiskDevice.teardown: sda ; status: True ; 16:12:53 DEBUG : DeviceFormat.teardown: device: /dev/sda ; status: False ; type: None ; 16:12:53 DEBUG : PartitionDevice.teardown: sda2 ; status: True ; 16:12:53 DEBUG : DeviceFormat.teardown: device: /dev/sda2 ; status: False ; type: None ; 16:12:53 DEBUG : DiskDevice.teardown: sda ; status: True ; 16:12:53 DEBUG : DeviceFormat.teardown: device: /dev/sda ; status: False ; type: None ; 16:12:53 DEBUG : PartitionDevice.teardown: sda3 ; status: True ; 16:12:53 DEBUG : LVMPhysicalVolume.teardown: device: /dev/sda3 ; status: None ; type: lvmpv ; 16:12:53 DEBUG : DiskDevice.teardown: sda ; status: True ; 16:12:53 DEBUG : DeviceFormat.teardown: device: /dev/sda ; status: False ; type: None ; 16:12:53 DEBUG : PartitionDevice.teardown: sda4 ; status: True ; 16:12:53 DEBUG : DeviceFormat.teardown: device: /dev/sda4 ; status: False ; type: None ; 16:12:53 DEBUG : DiskDevice.teardown: sda ; status: True ; 16:12:53 DEBUG : DeviceFormat.teardown: device: /dev/sda ; status: False ; type: None ; 16:12:53 DEBUG : PartitionDevice.teardown: sda5 ; status: True ; 16:12:53 DEBUG : SwapSpace.teardown: device: /dev/sda5 ; status: False ; type: swap ; 16:12:53 DEBUG : DiskDevice.teardown: sda ; status: True ; 16:12:53 DEBUG : DeviceFormat.teardown: device: /dev/sda ; status: False ; type: None ; 16:12:53 DEBUG : PartitionDevice.teardown: sda6 ; status: True ; 16:12:53 DEBUG : DiskDevice.teardown: sda ; status: True ; 16:12:53 DEBUG : DeviceFormat.teardown: device: /dev/sda ; status: False ; type: None ; 16:12:53 DEBUG : PartitionDevice.teardown: sda7 ; status: True ; 16:12:53 DEBUG : DiskDevice.teardown: sda ; status: True ; 16:12:53 DEBUG : DeviceFormat.teardown: device: /dev/sda ; status: False ; type: None ; 16:12:53 DEBUG : PartitionDevice.teardown: sda8 ; status: True ; 16:12:53 DEBUG : DiskDevice.teardown: sda ; status: True ; 16:12:53 DEBUG : DeviceFormat.teardown: device: /dev/sda ; status: False ; type: None ; 16:12:53 DEBUG : PartitionDevice.teardown: sda9 ; status: True ; 16:12:53 DEBUG : DeviceFormat.teardown: device: /dev/sda9 ; status: False ; type: None ; 16:12:53 DEBUG : DiskDevice.teardown: sda ; status: True ; 16:12:53 DEBUG : DeviceFormat.teardown: device: /dev/sda ; status: False ; type: None ; 16:12:53 DEBUG : PartitionDevice.teardown: sda10 ; status: True ; 16:12:53 DEBUG : DiskDevice.teardown: sda ; status: True ; 16:12:53 DEBUG : DeviceFormat.teardown: device: /dev/sda ; status: False ; type: None ; 16:12:53 DEBUG : LVMLogicalVolumeDevice.teardown: VolGroup-lv_root ; status: True ; 16:12:54 DEBUG : LVMVolumeGroupDevice.teardown: VolGroup ; status: True ; 16:12:54 DEBUG : PartitionDevice.teardown: sda11 ; status: True ; 16:12:54 DEBUG : LVMPhysicalVolume.teardown: device: /dev/sda11 ; status: False ; type: lvmpv ; 16:12:57 DEBUG : DiskDevice.teardown: sda ; status: True ; 16:12:57 DEBUG : DeviceFormat.teardown: device: /dev/sda ; status: False ; type: None ; 16:12:57 INFO : moving (1) to step network 16:13:19 INFO : moving (1) to step timezone 16:13:24 INFO : moving (1) to step accounts 16:13:32 INFO : moving (1) to step setuptime 21:43:33 INFO : moving (1) to step parttype 21:43:39 INFO : moving (1) to step autopartitionexecute 21:43:39 DEBUG : LVMLogicalVolumeDevice._setFormat: VolGroup-lv_root ; current: ext4 ; type: None ; 21:43:39 DEBUG : LVMLogicalVolumeDevice.teardown: VolGroup-lv_root ; status: False ; 21:43:39 DEBUG : LVMVolumeGroupDevice.removeChild: kids: 1 ; name: VolGroup ; 21:43:39 DEBUG : LVMVolumeGroupDevice.teardown: VolGroup ; status: True ; 21:43:40 DEBUG : PartitionDevice.removeChild: kids: 1 ; name: sda11 ; 21:43:40 DEBUG : PartitionDevice._setFormat: sda1 ; 21:43:40 DEBUG : PartitionDevice._setFormat: sda1 ; current: ext3 ; type: None ; 21:43:40 DEBUG : PartitionDevice.teardown: sda1 ; status: True ; 21:43:40 DEBUG : DeviceFormat.teardown: device: /dev/sda1 ; status: False ; type: None ; 21:43:40 DEBUG : DiskDevice.removeChild: kids: 11 ; name: sda ; 21:43:40 DEBUG : PartitionDevice._setFormat: sda10 ; 21:43:40 DEBUG : PartitionDevice._setFormat: sda10 ; current: ext3 ; type: None ; 21:43:40 DEBUG : PartitionDevice.teardown: sda10 ; status: True ; 21:43:40 DEBUG : DeviceFormat.teardown: device: /dev/sda10 ; status: False ; type: None ; 21:43:40 DEBUG : DiskDevice.removeChild: kids: 10 ; name: sda ; 21:43:40 DEBUG : LVMPhysicalVolume.teardown: device: /dev/sda11 ; status: False ; type: lvmpv ; 21:43:40 DEBUG : PartitionDevice._setFormat: sda10 ; 21:43:40 DEBUG : PartitionDevice._setFormat: sda10 ; current: lvmpv ; type: None ; 21:43:40 DEBUG : PartitionDevice.teardown: sda10 ; status: True ; 21:43:40 DEBUG : DeviceFormat.teardown: device: /dev/sda10 ; status: False ; type: None ; 21:43:40 DEBUG : DiskDevice.removeChild: kids: 9 ; name: sda ; 21:43:40 DEBUG : PartitionDevice.teardown: sda2 ; status: True ; 21:43:40 DEBUG : DeviceFormat.teardown: device: /dev/sda2 ; status: False ; type: None ; 21:43:40 DEBUG : DiskDevice.removeChild: kids: 8 ; name: sda ; 21:43:40 DEBUG : LVMPhysicalVolume.teardown: device: /dev/sda3 ; status: None ; type: lvmpv ; 21:43:40 DEBUG : PartitionDevice._setFormat: sda3 ; 21:43:40 DEBUG : PartitionDevice._setFormat: sda3 ; current: lvmpv ; type: None ; 21:43:40 DEBUG : PartitionDevice.teardown: sda3 ; status: True ; 21:43:40 DEBUG : DeviceFormat.teardown: device: /dev/sda3 ; status: False ; type: None ; 21:43:40 DEBUG : DiskDevice.removeChild: kids: 7 ; name: sda ; 21:43:40 DEBUG : SwapSpace.teardown: device: /dev/sda5 ; status: False ; type: swap ; 21:43:40 DEBUG : PartitionDevice._setFormat: sda5 ; 21:43:40 DEBUG : PartitionDevice._setFormat: sda5 ; current: swap ; type: None ; 21:43:40 DEBUG : PartitionDevice.teardown: sda5 ; status: True ; 21:43:40 DEBUG : DeviceFormat.teardown: device: /dev/sda5 ; status: False ; type: None ; 21:43:40 DEBUG : DiskDevice.removeChild: kids: 6 ; name: sda ; 21:43:40 DEBUG : PartitionDevice._setFormat: sda5 ; 21:43:40 DEBUG : PartitionDevice._setFormat: sda5 ; current: ext4 ; type: None ; 21:43:40 DEBUG : PartitionDevice.teardown: sda5 ; status: True ; 21:43:40 DEBUG : DeviceFormat.teardown: device: /dev/sda5 ; status: False ; type: None ; 21:43:40 DEBUG : DiskDevice.removeChild: kids: 5 ; name: sda ; 21:43:40 DEBUG : PartitionDevice._setFormat: sda5 ; 21:43:40 DEBUG : PartitionDevice._setFormat: sda5 ; current: ext4 ; type: None ; 21:43:40 DEBUG : PartitionDevice.teardown: sda5 ; status: True ; 21:43:40 DEBUG : DeviceFormat.teardown: device: /dev/sda5 ; status: False ; type: None ; 21:43:40 DEBUG : DiskDevice.removeChild: kids: 4 ; name: sda ; 21:43:40 DEBUG : PartitionDevice._setFormat: sda5 ; 21:43:40 DEBUG : PartitionDevice._setFormat: sda5 ; current: ext4 ; type: None ; 21:43:40 DEBUG : PartitionDevice.teardown: sda5 ; status: True ; 21:43:40 DEBUG : DeviceFormat.teardown: device: /dev/sda5 ; status: False ; type: None ; 21:43:40 DEBUG : DiskDevice.removeChild: kids: 3 ; name: sda ; 21:43:40 DEBUG : PartitionDevice.teardown: sda5 ; status: True ; 21:43:40 DEBUG : DeviceFormat.teardown: device: /dev/sda9 ; status: False ; type: None ; 21:43:40 DEBUG : DiskDevice.removeChild: kids: 2 ; name: sda ; 21:43:40 DEBUG : PartitionDevice.teardown: sda4 ; status: True ; 21:43:40 DEBUG : DeviceFormat.teardown: device: /dev/sda4 ; status: False ; type: None ; 21:43:40 DEBUG : DiskDevice.removeChild: kids: 1 ; name: sda ; 21:43:40 DEBUG : LVMPhysicalVolume.__init__: mountpoint: None ; 21:43:40 DEBUG : DiskDevice.addChild: kids: 0 ; name: sda ; 21:43:40 DEBUG : PartitionDevice._setFormat: req0 ; 21:43:40 DEBUG : PartitionDevice._setFormat: req0 ; current: None ; type: lvmpv ; 21:43:40 DEBUG : DiskDevice.removeChild: kids: 1 ; name: sda ; 21:43:40 DEBUG : Ext3FS.supported: supported: True ; 21:43:40 DEBUG : DiskDevice.addChild: kids: 0 ; name: sda ; 21:43:40 DEBUG : PartitionDevice._setFormat: req1 ; 21:43:40 DEBUG : PartitionDevice._setFormat: req1 ; current: None ; type: ext3 ; 21:43:40 DEBUG : DiskDevice.removeChild: kids: 1 ; name: sda ; 21:43:40 DEBUG : DiskDevice.setup: sda ; status: True ; 21:43:40 DEBUG : PartitionDevice._setPartedPartition: req1 ; 21:43:40 DEBUG : PartitionDevice._setDisk: sda1 ; new: DiskDevice instance (0x92caecc) -- description = name = sda status = True parents = [] kids = 0 id = 0 uuid = None format = size = 152625.344238 major = 8 minor = 0 exists = True sysfs path = /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda label = None target size = 0 path = /dev/sda format args = [] removable = False partedDevice = partedDisk = ; old: None ; 21:43:40 DEBUG : DiskDevice.addChild: kids: 0 ; name: sda ; 21:43:40 DEBUG : PartitionDevice._setPartedPartition: sda1 ; 21:43:40 DEBUG : PartitionDevice._setPartedPartition: req0 ; 21:43:40 DEBUG : PartitionDevice._setDisk: sda2 ; new: DiskDevice instance (0x92caecc) -- description = name = sda status = True parents = [] kids = 1 id = 0 uuid = None format = size = 152625.344238 major = 8 minor = 0 exists = True sysfs path = /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda label = None target size = 0 path = /dev/sda format args = [] removable = False partedDevice = partedDisk = ; old: None ; 21:43:40 DEBUG : DiskDevice.addChild: kids: 1 ; name: sda ; 21:43:40 DEBUG : PartitionDevice._setPartedPartition: sda2 ; 21:43:40 DEBUG : PartitionDevice._setPartedPartition: sda1 ; 21:43:40 DEBUG : PartitionDevice._setDisk: req1 ; new: None ; old: DiskDevice instance (0x92caecc) -- description = name = sda status = True parents = [] kids = 2 id = 0 uuid = None format = size = 152625.344238 major = 8 minor = 0 exists = True sysfs path = /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda label = None target size = 0 path = /dev/sda format args = [] removable = False partedDevice = partedDisk = ; 21:43:40 DEBUG : DiskDevice.removeChild: kids: 2 ; name: sda ; 21:43:40 DEBUG : PartitionDevice._setPartedPartition: sda2 ; 21:43:40 DEBUG : PartitionDevice._setDisk: req0 ; new: None ; old: DiskDevice instance (0x92caecc) -- description = name = sda status = True parents = [] kids = 1 id = 0 uuid = None format = size = 152625.344238 major = 8 minor = 0 exists = True sysfs path = /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda label = None target size = 0 path = /dev/sda format args = [] removable = False partedDevice = partedDisk = ; 21:43:40 DEBUG : DiskDevice.removeChild: kids: 1 ; name: sda ; 21:43:40 DEBUG : PartitionDevice._setPartedPartition: req1 ; 21:43:40 DEBUG : PartitionDevice._setDisk: sda1 ; new: DiskDevice instance (0x92caecc) -- description = name = sda status = True parents = [] kids = 0 id = 0 uuid = None format = size = 152625.344238 major = 8 minor = 0 exists = True sysfs path = /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda label = None target size = 0 path = /dev/sda format args = [] removable = False partedDevice = partedDisk = ; old: None ; 21:43:40 DEBUG : DiskDevice.addChild: kids: 0 ; name: sda ; 21:43:40 DEBUG : PartitionDevice._setPartedPartition: sda1 ; 21:43:40 DEBUG : PartitionDevice._setPartedPartition: req0 ; 21:43:40 DEBUG : PartitionDevice._setDisk: sda2 ; new: DiskDevice instance (0x92caecc) -- description = name = sda status = True parents = [] kids = 1 id = 0 uuid = None format = size = 152625.344238 major = 8 minor = 0 exists = True sysfs path = /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda label = None target size = 0 path = /dev/sda format args = [] removable = False partedDevice = partedDisk = ; old: None ; 21:43:40 DEBUG : DiskDevice.addChild: kids: 1 ; name: sda ; 21:43:40 DEBUG : PartitionDevice._setPartedPartition: sda2 ; 21:43:40 DEBUG : PartitionDevice.addChild: kids: 0 ; name: sda2 ; 21:43:40 DEBUG : LVMVolumeGroupDevice._setFormat: vg_parshwahost ; current: None ; type: None ; 21:43:40 DEBUG : Ext4FS.supported: supported: True ; 21:43:40 DEBUG : LVMVolumeGroupDevice.addChild: kids: 0 ; name: vg_parshwahost ; 21:43:40 DEBUG : LVMLogicalVolumeDevice._setFormat: vg_parshwahost-lv_root ; current: None ; type: ext4 ; 21:43:40 DEBUG : SwapSpace.__init__: mountpoint: None ; 21:43:40 DEBUG : LVMVolumeGroupDevice.addChild: kids: 1 ; name: vg_parshwahost ; 21:43:40 DEBUG : LVMLogicalVolumeDevice._setFormat: vg_parshwahost-lv_swap ; current: None ; type: swap ; 21:43:40 INFO : moving (1) to step partition 21:43:46 INFO : moving (1) to step storagedone 21:43:47 DEBUG : DiskDevice.teardown: sda ; status: True ; 21:43:47 DEBUG : DeviceFormat.teardown: device: /dev/sda ; status: False ; type: None ; 21:43:47 INFO : moving (1) to step enablefilesystems 21:43:47 DEBUG : PartitionDevice.teardown: sda1 ; status: False ; 21:43:47 DEBUG : DiskDevice.teardown: sda ; status: True ; 21:43:47 DEBUG : DeviceFormat.teardown: device: /dev/sda ; status: False ; type: None ; 21:43:47 DEBUG : LVMLogicalVolumeDevice.teardown: vg_parshwahost-lv_root ; status: False ; 21:43:47 DEBUG : LVMVolumeGroupDevice.teardown: vg_parshwahost ; status: False ; 21:43:47 DEBUG : PartitionDevice.teardown: sda2 ; status: False ; 21:43:47 DEBUG : DiskDevice.teardown: sda ; status: True ; 21:43:47 DEBUG : DeviceFormat.teardown: device: /dev/sda ; status: False ; type: None ; 21:43:47 DEBUG : LVMLogicalVolumeDevice.teardown: vg_parshwahost-lv_swap ; status: False ; 21:43:47 DEBUG : LVMVolumeGroupDevice.teardown: vg_parshwahost ; status: False ; 21:43:47 DEBUG : PartitionDevice.teardown: sda2 ; status: False ; 21:43:47 DEBUG : DiskDevice.teardown: sda ; status: True ; 21:43:47 DEBUG : DeviceFormat.teardown: device: /dev/sda ; status: False ; type: None ; 21:43:47 DEBUG : DiskDevice.resetPartedDisk: sda ; 21:43:47 DEBUG : LVMLogicalVolumeDevice.setup: VolGroup-lv_root ; status: False ; 21:43:47 DEBUG : LVMVolumeGroupDevice.setup: VolGroup ; status: True ; 21:43:48 DEBUG : Ext4FS.destroy: device: /dev/mapper/VolGroup-lv_root ; status: False ; type: ext4 ; 21:43:50 DEBUG : LVMLogicalVolumeDevice.teardown: VolGroup-lv_root ; status: True ; 21:43:54 DEBUG : LVMLogicalVolumeDevice.destroy: VolGroup-lv_root ; status: False ; 21:43:54 DEBUG : LVMLogicalVolumeDevice.teardown: VolGroup-lv_root ; status: False ; 21:43:54 DEBUG : PartitionDevice.setup: sda10 ; status: True ; 21:43:54 DEBUG : DiskDevice.setup: sda ; status: True ; 21:43:54 DEBUG : DeviceFormat.setup: device: /dev/sda ; status: False ; type: None ; 21:43:56 DEBUG : LVMVolumeGroupDevice.destroy: VolGroup ; status: True ; 21:43:56 DEBUG : PartitionDevice.setup: sda10 ; status: True ; 21:43:56 DEBUG : DiskDevice.setup: sda ; status: True ; 21:43:56 DEBUG : DeviceFormat.setup: device: /dev/sda ; status: False ; type: None ; 21:43:57 DEBUG : LVMVolumeGroupDevice.notifyKernel: VolGroup ; status: True ; 21:43:57 DEBUG : notifying kernel of 'change' event on device /sys 21:43:57 DEBUG : sysfs path '/sys/uevent' invalid 21:43:59 DEBUG : PartitionDevice.setup: sda10 ; status: True ; 21:43:59 DEBUG : DiskDevice.setup: sda ; status: True ; 21:43:59 DEBUG : DeviceFormat.setup: device: /dev/sda ; status: False ; type: None ; 21:43:59 DEBUG : Ext3FS.destroy: device: /dev/sda10 ; status: False ; type: ext3 ; 21:44:00 DEBUG : PartitionDevice.teardown: sda10 ; status: True ; 21:44:00 DEBUG : PartitionDevice.unsetFlag: path: /dev/sda10 ; flag: 6 ; part: parted.Partition instance -- disk: fileSystem: None number: 10 path: /dev/sda10 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94b20ec> ; 21:44:00 DEBUG : PartitionDevice.flagAvailable: path: /dev/sda10 ; flag: 6 ; part: parted.Partition instance -- disk: fileSystem: None number: 10 path: /dev/sda10 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94b20ec> ; 21:44:00 DEBUG : DiskDevice.commit: sda ; status: True ; 21:44:00 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:02 DEBUG : PartitionDevice.setup: sda10 ; status: True ; 21:44:02 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:02 DEBUG : DeviceFormat.setup: device: /dev/sda ; status: False ; type: None ; 21:44:02 DEBUG : LVMPhysicalVolume.destroy: device: /dev/sda11 ; status: False ; type: lvmpv ; 21:44:03 DEBUG : LVMPhysicalVolume.notifyKernel: device: /dev/sda11 ; type: lvmpv ; 21:44:03 DEBUG : notifying kernel of 'change' event on device /sys/class/block/sda11 21:44:05 DEBUG : PartitionDevice.teardown: sda10 ; status: True ; 21:44:05 DEBUG : PartitionDevice.destroy: sda10 ; status: True ; 21:44:05 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:05 DEBUG : DiskDevice.removePartition: sda ; part: sda10 ; 21:44:05 DEBUG : DiskDevice.commit: sda ; status: True ; 21:44:05 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:08 DEBUG : PartitionDevice.destroy: sda10 ; status: True ; 21:44:08 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:08 DEBUG : DiskDevice.removePartition: sda ; part: sda10 ; 21:44:08 DEBUG : DiskDevice.commit: sda ; status: True ; 21:44:08 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:10 DEBUG : PartitionDevice.unsetFlag: path: /dev/sda5 ; flag: 3 ; part: parted.Partition instance -- disk: fileSystem: number: 5 path: /dev/sda5 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94a7f2c> ; 21:44:10 DEBUG : PartitionDevice.flagAvailable: path: /dev/sda5 ; flag: 3 ; part: parted.Partition instance -- disk: fileSystem: number: 5 path: /dev/sda5 type: 1 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94a7f2c> ; 21:44:10 DEBUG : DiskDevice.commit: sda ; status: True ; 21:44:10 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:12 DEBUG : PartitionDevice.setup: sda5 ; status: True ; 21:44:12 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:12 DEBUG : DeviceFormat.setup: device: /dev/sda ; status: False ; type: None ; 21:44:12 DEBUG : SwapSpace.destroy: device: /dev/sda5 ; status: False ; type: swap ; 21:44:12 DEBUG : PartitionDevice.teardown: sda5 ; status: True ; 21:44:12 DEBUG : PartitionDevice.setup: sda5 ; status: True ; 21:44:12 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:12 DEBUG : DeviceFormat.setup: device: /dev/sda ; status: False ; type: None ; 21:44:12 DEBUG : Ext4FS.destroy: device: /dev/sda6 ; status: False ; type: ext4 ; 21:44:13 DEBUG : PartitionDevice.teardown: sda5 ; status: True ; 21:44:13 DEBUG : PartitionDevice.setup: sda5 ; status: True ; 21:44:13 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:13 DEBUG : DeviceFormat.setup: device: /dev/sda ; status: False ; type: None ; 21:44:13 DEBUG : Ext4FS.destroy: device: /dev/sda7 ; status: False ; type: ext4 ; 21:44:13 DEBUG : PartitionDevice.teardown: sda5 ; status: True ; 21:44:13 DEBUG : PartitionDevice.setup: sda5 ; status: True ; 21:44:13 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:13 DEBUG : DeviceFormat.setup: device: /dev/sda ; status: False ; type: None ; 21:44:13 DEBUG : Ext4FS.destroy: device: /dev/sda8 ; status: False ; type: ext4 ; 21:44:14 DEBUG : PartitionDevice.teardown: sda5 ; status: True ; 21:44:14 DEBUG : PartitionDevice.destroy: sda5 ; status: True ; 21:44:14 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:14 DEBUG : DiskDevice.removePartition: sda ; part: sda5 ; 21:44:14 DEBUG : DiskDevice.commit: sda ; status: True ; 21:44:14 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:15 DEBUG : PartitionDevice.destroy: sda5 ; status: True ; 21:44:15 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:15 DEBUG : DiskDevice.removePartition: sda ; part: sda5 ; 21:44:15 DEBUG : DiskDevice.commit: sda ; status: True ; 21:44:15 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:17 DEBUG : PartitionDevice.destroy: sda5 ; status: True ; 21:44:17 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:17 DEBUG : DiskDevice.removePartition: sda ; part: sda5 ; 21:44:17 DEBUG : DiskDevice.commit: sda ; status: True ; 21:44:17 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:19 DEBUG : PartitionDevice.destroy: sda5 ; status: True ; 21:44:19 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:19 DEBUG : DiskDevice.removePartition: sda ; part: sda5 ; 21:44:19 DEBUG : DiskDevice.commit: sda ; status: True ; 21:44:19 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:21 DEBUG : PartitionDevice.destroy: sda5 ; status: True ; 21:44:21 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:21 DEBUG : DiskDevice.removePartition: sda ; part: sda5 ; 21:44:21 DEBUG : DiskDevice.commit: sda ; status: True ; 21:44:21 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:23 DEBUG : PartitionDevice.destroy: sda4 ; status: True ; 21:44:23 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:23 DEBUG : DiskDevice.removePartition: sda ; part: sda4 ; 21:44:23 DEBUG : DiskDevice.commit: sda ; status: True ; 21:44:23 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:24 DEBUG : PartitionDevice.unsetFlag: path: /dev/sda3 ; flag: 6 ; part: parted.Partition instance -- disk: fileSystem: None number: 3 path: /dev/sda3 type: 0 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94a7e6c> ; 21:44:24 DEBUG : PartitionDevice.flagAvailable: path: /dev/sda3 ; flag: 6 ; part: parted.Partition instance -- disk: fileSystem: None number: 3 path: /dev/sda3 type: 0 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x94a7e6c> ; 21:44:24 DEBUG : DiskDevice.commit: sda ; status: True ; 21:44:24 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:25 DEBUG : PartitionDevice.setup: sda3 ; status: True ; 21:44:25 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:25 DEBUG : DeviceFormat.setup: device: /dev/sda ; status: False ; type: None ; 21:44:25 DEBUG : LVMPhysicalVolume.destroy: device: /dev/sda3 ; status: None ; type: lvmpv ; 21:44:26 DEBUG : LVMPhysicalVolume.notifyKernel: device: /dev/sda3 ; type: lvmpv ; 21:44:26 DEBUG : notifying kernel of 'change' event on device /sys/class/block/sda3 21:44:28 DEBUG : PartitionDevice.teardown: sda3 ; status: True ; 21:44:28 DEBUG : PartitionDevice.destroy: sda3 ; status: True ; 21:44:28 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:28 DEBUG : DiskDevice.removePartition: sda ; part: sda3 ; 21:44:28 DEBUG : DiskDevice.commit: sda ; status: True ; 21:44:28 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:29 DEBUG : PartitionDevice.destroy: sda2 ; status: True ; 21:44:29 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:29 DEBUG : DiskDevice.removePartition: sda ; part: sda2 ; 21:44:29 DEBUG : DiskDevice.commit: sda ; status: True ; 21:44:29 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:31 DEBUG : PartitionDevice.setup: sda1 ; status: True ; 21:44:31 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:31 DEBUG : DeviceFormat.setup: device: /dev/sda ; status: False ; type: None ; 21:44:31 DEBUG : Ext3FS.destroy: device: /dev/sda1 ; status: False ; type: ext3 ; 21:44:31 DEBUG : PartitionDevice.teardown: sda1 ; status: True ; 21:44:31 DEBUG : PartitionDevice.destroy: sda1 ; status: True ; 21:44:31 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:31 DEBUG : DiskDevice.removePartition: sda ; part: sda1 ; 21:44:31 DEBUG : DiskDevice.commit: sda ; status: True ; 21:44:31 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:32 DEBUG : PartitionDevice.create: sda1 ; status: False ; 21:44:32 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:32 DEBUG : DiskDevice.addPartition: sda ; part: sda1 ; 21:44:32 DEBUG : DiskDevice.commit: sda ; status: True ; 21:44:32 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:33 DEBUG : DeviceFormat.destroy: device: /dev/sda1 ; status: False ; type: None ; 21:44:33 DEBUG : PartitionDevice._setPartedPartition: sda1 ; 21:44:33 DEBUG : PartitionDevice.setup: sda1 ; status: True ; 21:44:33 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:33 DEBUG : DeviceFormat.setup: device: /dev/sda ; status: False ; type: None ; 21:44:34 DEBUG : PartitionDevice.setup: sda1 ; status: True ; 21:44:34 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:34 DEBUG : DeviceFormat.setup: device: /dev/sda ; status: False ; type: None ; 21:44:34 DEBUG : Ext3FS.create: device: None ; status: False ; type: ext3 ; 21:44:34 DEBUG : Ext3FS.doFormat: device: /dev/sda1 ; mountpoint: /boot ; type: ext3 ; 21:44:41 DEBUG : Ext3FS.notifyKernel: device: /dev/sda1 ; type: ext3 ; 21:44:41 DEBUG : notifying kernel of 'change' event on device /sys/class/block/sda1 21:44:41 DEBUG : PartitionDevice.updateSysfsPath: sda1 ; status: True ; 21:44:41 DEBUG : PartitionDevice.updateSysfsPath: sda1 ; status: True ; 21:44:41 DEBUG : PartitionDevice.create: sda2 ; status: False ; 21:44:41 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:41 DEBUG : DiskDevice.addPartition: sda ; part: sda2 ; 21:44:41 DEBUG : DiskDevice.commit: sda ; status: True ; 21:44:42 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:42 DEBUG : DeviceFormat.destroy: device: /dev/sda2 ; status: False ; type: None ; 21:44:42 DEBUG : PartitionDevice._setPartedPartition: sda2 ; 21:44:42 DEBUG : PartitionDevice.setup: sda2 ; status: True ; 21:44:42 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:42 DEBUG : DeviceFormat.setup: device: /dev/sda ; status: False ; type: None ; 21:44:42 DEBUG : PartitionDevice.setFlag: path: /dev/sda2 ; flag: 6 ; part: parted.Partition instance -- disk: fileSystem: None number: 2 path: /dev/sda2 type: 0 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x96cdc8c> ; 21:44:42 DEBUG : PartitionDevice.flagAvailable: path: /dev/sda2 ; flag: 6 ; part: parted.Partition instance -- disk: fileSystem: None number: 2 path: /dev/sda2 type: 0 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x96cdc8c> ; 21:44:42 DEBUG : DiskDevice.commit: sda ; status: True ; 21:44:42 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:43 DEBUG : PartitionDevice.setup: sda2 ; status: True ; 21:44:43 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:43 DEBUG : DeviceFormat.setup: device: /dev/sda ; status: False ; type: None ; 21:44:43 DEBUG : LVMPhysicalVolume.create: device: None ; status: None ; type: lvmpv ; 21:44:43 DEBUG : LVMPhysicalVolume.create: device: None ; status: None ; type: lvmpv ; 21:44:43 DEBUG : LVMPhysicalVolume.destroy: device: /dev/sda2 ; status: None ; type: lvmpv ; 21:44:43 DEBUG : LVMPhysicalVolume.notifyKernel: device: /dev/sda2 ; type: lvmpv ; 21:44:43 DEBUG : notifying kernel of 'change' event on device /sys/class/block/sda2 21:44:43 DEBUG : PartitionDevice.updateSysfsPath: sda2 ; status: True ; 21:44:43 DEBUG : PartitionDevice.updateSysfsPath: sda2 ; status: True ; 21:44:43 DEBUG : LVMVolumeGroupDevice.create: vg_parshwahost ; status: False ; 21:44:43 DEBUG : PartitionDevice.setup: sda2 ; status: True ; 21:44:43 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:43 DEBUG : DeviceFormat.setup: device: /dev/sda ; status: False ; type: None ; 21:44:43 DEBUG : LVMVolumeGroupDevice.setup: vg_parshwahost ; status: False ; 21:44:43 DEBUG : PartitionDevice.setup: sda2 ; status: True ; 21:44:43 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:43 DEBUG : DeviceFormat.setup: device: /dev/sda ; status: False ; type: None ; 21:44:44 DEBUG : LVMLogicalVolumeDevice.create: vg_parshwahost-lv_root ; status: False ; 21:44:44 DEBUG : LVMVolumeGroupDevice.setup: vg_parshwahost ; status: False ; 21:44:44 DEBUG : PartitionDevice.setup: sda2 ; status: True ; 21:44:44 DEBUG : DiskDevice.setup: sda ; status: True ; 21:44:44 DEBUG : DeviceFormat.setup: device: /dev/sda ; status: False ; type: None ; /tmp/program.log: Running... ['udevadm', 'trigger', '--subsystem-match=block'] Running... ['udevadm', 'settle', '--timeout=30'] Running... ['dumpe2fs', '-h', '/dev/sda1'] Filesystem volume name: Last mounted on: Filesystem UUID: 78832b2b-e6cc-49a3-98ed-53e66023a9f2 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype sparse_super Filesystem flags: signed_directory_hash Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 51200 Block count: 204800 Reserved block count: 10240 Free blocks: 192674 Free inodes: 51189 First block: 1 Block size: 1024 Fragment size: 1024 Reserved GDT blocks: 256 Blocks per group: 8192 Fragments per group: 8192 Inodes per group: 2048 Inode blocks per group: 256 Filesystem created: Fri Oct 9 09:50:17 2009 Last mount time: n/a Last write time: Fri Oct 9 09:50:18 2009 Mount count: 0 Maximum mount count: 31 Last checked: Fri Oct 9 09:50:17 2009 Check interval: 15552000 (6 months) Next check after: Wed Apr 7 09:50:17 2010 Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 128 Journal inode: 8 Default directory hash: half_md4 Directory Hash Seed: d20f274f-0b95-4990-81ab-1fbc568a14ab Journal backup: inode blocks Journal size: 4113k dumpe2fs 1.41.4 (27-Jan-2009) Running... ['resize2fs', '-P', '/dev/sda1'] Estimated minimum size of the filesystem: 4644 resize2fs 1.41.4 (27-Jan-2009) Running... ['dumpe2fs', '-h', '/dev/sda6'] Filesystem volume name: Last mounted on: Filesystem UUID: 06b3af73-3a68-4831-abaa-7cb6dbc65f2d Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Filesystem flags: signed_directory_hash Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 320000 Block count: 1279999 Reserved block count: 63999 Free blocks: 1224633 Free inodes: 319989 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 312 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8000 Inode blocks per group: 500 Flex block group size: 16 Filesystem created: Fri Oct 9 09:50:27 2009 Last mount time: n/a Last write time: Fri Oct 9 09:50:29 2009 Mount count: 0 Maximum mount count: 22 Last checked: Fri Oct 9 09:50:27 2009 Check interval: 15552000 (6 months) Next check after: Wed Apr 7 09:50:27 2010 Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode: 8 Default directory hash: half_md4 Directory Hash Seed: 6a558fe4-e616-4bf3-a9f4-c96ac1b90862 Journal backup: inode blocks Journal size: 128M dumpe2fs 1.41.4 (27-Jan-2009) Running... ['resize2fs', '-P', '/dev/sda6'] Estimated minimum size of the filesystem: 44412 resize2fs 1.41.4 (27-Jan-2009) Running... ['dumpe2fs', '-h', '/dev/sda7'] Filesystem volume name: Last mounted on: Filesystem UUID: 8a891d79-6cfe-451e-a823-1de04308919a Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Filesystem flags: signed_directory_hash Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 320000 Block count: 1279999 Reserved block count: 63999 Free blocks: 1224633 Free inodes: 319989 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 312 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8000 Inode blocks per group: 500 Flex block group size: 16 Filesystem created: Fri Oct 9 09:50:32 2009 Last mount time: n/a Last write time: Fri Oct 9 09:50:34 2009 Mount count: 0 Maximum mount count: 36 Last checked: Fri Oct 9 09:50:32 2009 Check interval: 15552000 (6 months) Next check after: Wed Apr 7 09:50:32 2010 Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode: 8 Default directory hash: half_md4 Directory Hash Seed: b5c8083d-7737-4d54-9d50-75f820c74ac7 Journal backup: inode blocks Journal size: 128M dumpe2fs 1.41.4 (27-Jan-2009) Running... ['resize2fs', '-P', '/dev/sda7'] Estimated minimum size of the filesystem: 44412 resize2fs 1.41.4 (27-Jan-2009) Running... ['dumpe2fs', '-h', '/dev/sda8'] Filesystem volume name: Last mounted on: Filesystem UUID: 9f73e989-7e77-4e53-8896-4053929ee4b8 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Filesystem flags: signed_directory_hash Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 320000 Block count: 1279999 Reserved block count: 63999 Free blocks: 1224633 Free inodes: 319989 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 312 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8000 Inode blocks per group: 500 Flex block group size: 16 Filesystem created: Fri Oct 9 09:50:37 2009 Last mount time: n/a Last write time: Fri Oct 9 09:50:40 2009 Mount count: 0 Maximum mount count: 39 Last checked: Fri Oct 9 09:50:37 2009 Check interval: 15552000 (6 months) Next check after: Wed Apr 7 09:50:37 2010 Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode: 8 Default directory hash: half_md4 Directory Hash Seed: 033c3447-47fd-4f73-a04c-b7f74c06fb6d Journal backup: inode blocks Journal size: 128M dumpe2fs 1.41.4 (27-Jan-2009) Running... ['resize2fs', '-P', '/dev/sda8'] Estimated minimum size of the filesystem: 44412 resize2fs 1.41.4 (27-Jan-2009) Running... ['dumpe2fs', '-h', '/dev/sda10'] Filesystem volume name: Last mounted on: Filesystem UUID: 2d189a9c-eb0e-49b0-a9d3-1dc36acd61eb Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype sparse_super Filesystem flags: signed_directory_hash Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 51200 Block count: 204796 Reserved block count: 10239 Free blocks: 192670 Free inodes: 51189 First block: 1 Block size: 1024 Fragment size: 1024 Reserved GDT blocks: 256 Blocks per group: 8192 Fragments per group: 8192 Inodes per group: 2048 Inode blocks per group: 256 Filesystem created: Fri Oct 9 09:52:12 2009 Last mount time: n/a Last write time: Fri Oct 9 09:52:12 2009 Mount count: 0 Maximum mount count: 24 Last checked: Fri Oct 9 09:52:12 2009 Check interval: 15552000 (6 months) Next check after: Wed Apr 7 09:52:12 2010 Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 128 Journal inode: 8 Default directory hash: half_md4 Directory Hash Seed: 8eb0fa90-69c0-453e-9526-ae6606ba08d0 Journal backup: inode blocks Journal size: 4113k dumpe2fs 1.41.4 (27-Jan-2009) Running... ['resize2fs', '-P', '/dev/sda10'] Estimated minimum size of the filesystem: 4644 resize2fs 1.41.4 (27-Jan-2009) Running... ['lvm', 'lvchange', '-a', 'y', 'VolGroup/lv_root'] Running... ['dmsetup', 'info', '--columns', '--noheadings', '-o', 'devno', 'VolGroup'] Device does not exist. Command failed Running... ['dmsetup', 'info', '--columns', '--noheadings', '-o', 'devno', 'VolGroup'] Device does not exist. Command failed Running... ['udevadm', 'settle', '--timeout=30'] Running... ['dumpe2fs', '-h', '/dev/mapper/VolGroup-lv_root'] Filesystem volume name: Last mounted on: Filesystem UUID: 5e1620a1-9533-4021-b0bc-145d9276d807 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Filesystem flags: signed_directory_hash Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 6365184 Block count: 25446400 Reserved block count: 1272320 Free blocks: 24998873 Free inodes: 6365173 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 1017 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 Flex block group size: 16 Filesystem created: Fri Oct 9 09:52:24 2009 Last mount time: n/a Last write time: Fri Oct 9 09:53:22 2009 Mount count: 0 Maximum mount count: 30 Last checked: Fri Oct 9 09:52:24 2009 Check interval: 15552000 (6 months) Next check after: Wed Apr 7 09:52:24 2010 Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode: 8 Default directory hash: half_md4 Directory Hash Seed: 34b54ca1-0738-4823-80d5-888c8f11d8bb Journal backup: inode blocks Journal size: 128M dumpe2fs 1.41.4 (27-Jan-2009) Running... ['resize2fs', '-P', '/dev/mapper/VolGroup-lv_root'] Estimated minimum size of the filesystem: 94367 resize2fs 1.41.4 (27-Jan-2009) Running... ['udevadm', 'settle', '--timeout=30'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['lvm', 'lvchange', '-a', 'n', 'VolGroup/lv_root'] Running... ['lvm', 'vgchange', '-a', 'n', 'VolGroup'] 0 logical volume(s) in volume group "VolGroup" now active /dev/dm-2: open failed: No such device or address Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['/usr/sbin/hwclock', '--hctosys', '-u'] Running... ['lvm', 'vgchange', '-a', 'n', 'VolGroup'] 0 logical volume(s) in volume group "VolGroup" now active Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['swapoff', '-a'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['lvm', 'lvchange', '-a', 'y', 'VolGroup/lv_root'] Running... ['udevadm', 'settle'] Running... ['lvm', 'lvchange', '-a', 'n', 'VolGroup/lv_root'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['lvm', 'lvremove', 'VolGroup/lv_root'] Logical volume "lv_root" successfully removed Running... ['udevadm', 'settle', '--timeout=10'] Running... ['lvm', 'vgreduce', '--removemissing', 'VolGroup'] Volume group "VolGroup" is already consistent Running... ['lvm', 'vgremove', 'VolGroup'] Volume group "VolGroup" successfully removed Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle'] Running... ['udevadm', 'settle'] Running... ['lvm', 'pvremove', '/dev/sda11'] Labels on physical volume "/dev/sda11" successfully wiped Running... ['udevadm', 'settle'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle'] Running... ['udevadm', 'settle'] Running... ['udevadm', 'settle'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle'] Running... ['udevadm', 'settle'] Running... ['lvm', 'pvremove', '/dev/sda3'] Labels on physical volume "/dev/sda3" successfully wiped Running... ['udevadm', 'settle'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle'] Running... ['mke2fs', '-t', 'ext3', '/dev/sda1'] Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 320000 inodes, 1280000 blocks 64000 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=1312817152 40 block groups 32768 blocks per group, 32768 fragments per group 8000 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736 Writing inode tables: 0/40 1/40 2/40 3/40 4/40 5/40 6/40 7/40 8/40 9/4010/4011/4012/4013/4014/4015/4016/4017/4018/4019/4020/4021/4022/4023/4024/4025/4026/4027/4028/4029/4030/4031/4032/4033/4034/4035/4036/4037/4038/4039/40done Creating journal (32768 blocks): done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 20 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. Running... ['/usr/sbin/tune2fs', '-c0', '-i0', '-ouser_xattr,acl', '/dev/sda1'] Running... ['udevadm', 'settle'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['udevadm', 'settle'] Running... ['udevadm', 'settle'] Running... ['lvm', 'pvcreate', '/dev/sda2'] Physical volume "/dev/sda2" successfully created Running... ['udevadm', 'settle'] Running... ['udevadm', 'settle', '--timeout=10'] Running... ['lvm', 'vgcreate', '-s', '4m', 'vg_parshwahost', '/dev/sda2'] Volume group "vg_parshwahost" successfully created Running... ['udevadm', 'settle', '--timeout=10'] Running... ['lvm', 'lvcreate', '-L', '150408m', '-n', 'lv_root', 'vg_parshwahost'] Insufficient free extents (2499) in volume group vg_parshwahost: 37602 required /tmp/storage.log: [2009-10-09 16:12:33,817] DEBUG: registered device format class LUKS as luks [2009-10-09 16:12:33,818] DEBUG: registered device format class DMRaidMember as dmraidmember [2009-10-09 16:12:33,820] DEBUG: registered device format class SwapSpace as swap [2009-10-09 16:12:33,821] DEBUG: registered device format class PPCPRePBoot as prepboot [2009-10-09 16:12:33,823] DEBUG: registered device format class Ext2FS as ext2 [2009-10-09 16:12:33,824] DEBUG: registered device format class Ext3FS as ext3 [2009-10-09 16:12:33,824] DEBUG: registered device format class Ext4FS as ext4 [2009-10-09 16:12:33,825] DEBUG: registered device format class FATFS as vfat [2009-10-09 16:12:33,825] DEBUG: registered device format class EFIFS as efi [2009-10-09 16:12:33,826] DEBUG: registered device format class BTRFS as btrfs [2009-10-09 16:12:33,826] DEBUG: registered device format class GFS2 as gfs2 [2009-10-09 16:12:33,826] DEBUG: registered device format class JFS as jfs [2009-10-09 16:12:33,827] DEBUG: registered device format class XFS as xfs [2009-10-09 16:12:33,827] DEBUG: registered device format class HFS as hfs [2009-10-09 16:12:33,828] DEBUG: registered device format class AppleBootstrapFS as appleboot [2009-10-09 16:12:33,828] DEBUG: registered device format class HFSPlus as hfs+ [2009-10-09 16:12:33,828] DEBUG: registered device format class NTFS as ntfs [2009-10-09 16:12:33,829] DEBUG: registered device format class NFS as nfs [2009-10-09 16:12:33,829] DEBUG: registered device format class NFSv4 as nfs4 [2009-10-09 16:12:33,830] DEBUG: registered device format class Iso9660FS as iso9660 [2009-10-09 16:12:33,830] DEBUG: registered device format class NoDevFS as nodev [2009-10-09 16:12:33,830] DEBUG: registered device format class DevPtsFS as devpts [2009-10-09 16:12:33,831] DEBUG: registered device format class ProcFS as proc [2009-10-09 16:12:33,831] DEBUG: registered device format class SysFS as sysfs [2009-10-09 16:12:33,831] DEBUG: registered device format class TmpFS as tmpfs [2009-10-09 16:12:33,832] DEBUG: registered device format class BindFS as bind [2009-10-09 16:12:33,833] DEBUG: registered device format class MDRaidMember as mdmember [2009-10-09 16:12:33,834] DEBUG: registered device format class LVMPhysicalVolume as lvmpv [2009-10-09 16:12:43,284] INFO: sr0 looks to be the live device; ignoring [2009-10-09 16:12:43,287] INFO: devices to scan: ['sda', 'sda1', 'sda2', 'sda3', 'sda4', 'sda5', 'sda6', 'sda7', 'sda8', 'sda9', 'sda10', 'sda11', 'dm-0', 'dm-1'] [2009-10-09 16:12:43,673] DEBUG: scanning sda (/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda)... [2009-10-09 16:12:43,673] DEBUG: looking for device 'sda'... [2009-10-09 16:12:43,673] DEBUG: found None [2009-10-09 16:12:43,676] DEBUG: sda is a disk [2009-10-09 16:12:43,677] DEBUG: getFormat('None') returning DeviceFormat instance [2009-10-09 16:12:43,685] DEBUG: looking up parted Device: /dev/sda [2009-10-09 16:12:43,685] DEBUG: looking up parted Device: /dev/sda [2009-10-09 16:12:43,694] DEBUG: creating parted Disk: /dev/sda [2009-10-09 16:12:49,625] DEBUG: added sda (disk) to device tree [2009-10-09 16:12:49,628] DEBUG: {'DKD_PARTITION_TABLE': '1', 'ID_REVISION': '4.AA', 'ID_VENDOR_ENC': 'ATA\\x20\\x20\\x20\\x20\\x20', 'ID_ATA_COMPAT': 'ST3160215AS_6RAF8TR9', 'ID_PATH': 'pci-0000:00:1f.2-scsi-0:0:0:0', 'ID_VENDOR': 'ATA', 'ID_SERIAL': 'SATA_ST3160215AS_6RAF8TR9', 'DKD_PARTITION_TABLE_SCHEME': 'mbr', 'DEVTYPE': 'disk', 'ID_BUS': 'scsi', 'ID_MODEL': 'ST3160215AS', 'MAJOR': '8', 'sysfs_path': '/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda', 'ID_TYPE': 'disk', 'MINOR': '0', 'symlinks': ['block/8:0', 'disk/by-id/scsi-SATA_ST3160215AS_6RAF8TR9', 'disk/by-id/ata-ST3160215AS_6RAF8TR9', 'disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0'], 'ID_SERIAL_SHORT': '6RAF8TR9', 'name': 'sda', 'DKD_ATA_SMART_IS_AVAILABLE': '1', 'ANACBIN': '/sbin', 'ID_MODEL_ENC': 'ST3160215AS\\x20\\x20\\x20\\x20\\x20', 'DKD_MEDIA_AVAILABLE': '1'} [2009-10-09 16:12:49,629] DEBUG: no type or existing type for sda, bailing [2009-10-09 16:12:49,631] DEBUG: scanning sda1 (/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda1)... [2009-10-09 16:12:49,632] DEBUG: looking for device 'sda1'... [2009-10-09 16:12:49,633] DEBUG: found None [2009-10-09 16:12:49,633] DEBUG: sda1 is a partition [2009-10-09 16:12:49,636] DEBUG: looking for device 'sda'... [2009-10-09 16:12:49,637] DEBUG: found DiskDevice instance (0x92caecc) -- description = name = sda status = True parents = [] kids = 0 id = 0 uuid = None format = size = 152625.344238 major = 8 minor = 0 exists = True sysfs path = /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda label = None target size = 0 path = /dev/sda format args = [] removable = False partedDevice = partedDisk = [2009-10-09 16:12:49,643] DEBUG: getFormat('None') returning DeviceFormat instance [2009-10-09 16:12:49,647] DEBUG: looking up parted Partition: /dev/sda1 [2009-10-09 16:12:49,650] DEBUG: looking up parted Device: /dev/sda1 [2009-10-09 16:12:49,659] DEBUG: added sda1 (partition) to device tree [2009-10-09 16:12:49,660] DEBUG: {'ID_REVISION': '4.AA', 'ID_VENDOR_ENC': 'ATA\\x20\\x20\\x20\\x20\\x20', 'ID_ATA_COMPAT': 'ST3160215AS_6RAF8TR9', 'DKD_PARTITION_SIZE': '5242880000', 'ID_FS_VERSION': '1.0', 'ID_PATH': 'pci-0000:00:1f.2-scsi-0:0:0:0', 'ID_VENDOR': 'ATA', 'DKD_PARTITION_NUMBER': '1', 'ID_SERIAL': 'SATA_ST3160215AS_6RAF8TR9', 'DKD_PARTITION': '1', 'MINOR': '1', 'DEVTYPE': 'partition', 'ID_FS_UUID': '78832b2b-e6cc-49a3-98ed-53e66023a9f2', 'ID_FS_UUID_ENC': '78832b2b-e6cc-49a3-98ed-53e66023a9f2', 'ID_FS_TYPE': 'ext3', 'DKD_PARTITION_TYPE': '0x83', 'ID_MODEL': 'ST3160215AS', 'MAJOR': '8', 'sysfs_path': '/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda1', 'ID_FS_USAGE': 'filesystem', 'ID_TYPE': 'disk', 'DKD_PARTITION_SCHEME': 'mbr', 'ID_BUS': 'scsi', 'symlinks': ['block/8:1', 'disk/by-id/scsi-SATA_ST3160215AS_6RAF8TR9-part1', 'disk/by-id/ata-ST3160215AS_6RAF8TR9-part1', 'disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part1', 'disk/by-uuid/78832b2b-e6cc-49a3-98ed-53e66023a9f2'], 'ID_SERIAL_SHORT': '6RAF8TR9', 'name': 'sda1', 'ANACBIN': '/sbin', 'ID_MODEL_ENC': 'ST3160215AS\\x20\\x20\\x20\\x20\\x20'} [2009-10-09 16:12:49,660] DEBUG: type detected on 'sda1' is 'ext3' [2009-10-09 16:12:49,720] DEBUG: getFormat('ext3') returning Ext3FS instance [2009-10-09 16:12:49,728] DEBUG: scanning sda2 (/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda2)... [2009-10-09 16:12:49,728] DEBUG: looking for device 'sda2'... [2009-10-09 16:12:49,729] DEBUG: found None [2009-10-09 16:12:49,729] DEBUG: sda2 is a partition [2009-10-09 16:12:49,732] DEBUG: looking for device 'sda'... [2009-10-09 16:12:49,733] DEBUG: found DiskDevice instance (0x92caecc) -- description = name = sda status = True parents = [] kids = 1 id = 0 uuid = None format = size = 152625.344238 major = 8 minor = 0 exists = True sysfs path = /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda label = None target size = 0 path = /dev/sda format args = [] removable = False partedDevice = partedDisk = [2009-10-09 16:12:49,740] DEBUG: getFormat('None') returning DeviceFormat instance [2009-10-09 16:12:49,745] DEBUG: looking up parted Partition: /dev/sda2 [2009-10-09 16:12:49,748] DEBUG: looking up parted Device: /dev/sda2 [2009-10-09 16:12:49,758] DEBUG: added sda2 (partition) to device tree [2009-10-09 16:12:49,760] DEBUG: {'ID_REVISION': '4.AA', 'DKD_PARTITION_SIZE': '10485760000', 'ID_ATA_COMPAT': 'ST3160215AS_6RAF8TR9', 'ID_PATH': 'pci-0000:00:1f.2-scsi-0:0:0:0', 'ID_VENDOR': 'ATA', 'DKD_PARTITION_NUMBER': '2', 'ID_SERIAL': 'SATA_ST3160215AS_6RAF8TR9', 'DKD_PARTITION': '1', 'DEVTYPE': 'partition', 'ID_BUS': 'scsi', 'ID_VENDOR_ENC': 'ATA\\x20\\x20\\x20\\x20\\x20', 'DKD_PARTITION_TYPE': '0xfd', 'ID_MODEL': 'ST3160215AS', 'MAJOR': '8', 'sysfs_path': '/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda2', 'ID_TYPE': 'disk', 'DKD_PARTITION_SCHEME': 'mbr', 'MINOR': '2', 'symlinks': ['block/8:2', 'disk/by-id/scsi-SATA_ST3160215AS_6RAF8TR9-part2', 'disk/by-id/ata-ST3160215AS_6RAF8TR9-part2', 'disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part2'], 'ID_SERIAL_SHORT': '6RAF8TR9', 'name': 'sda2', 'ANACBIN': '/sbin', 'ID_MODEL_ENC': 'ST3160215AS\\x20\\x20\\x20\\x20\\x20'} [2009-10-09 16:12:49,760] DEBUG: no type or existing type for sda2, bailing [2009-10-09 16:12:49,761] DEBUG: scanning sda3 (/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda3)... [2009-10-09 16:12:49,761] DEBUG: looking for device 'sda3'... [2009-10-09 16:12:49,762] DEBUG: found None [2009-10-09 16:12:49,762] DEBUG: sda3 is a partition [2009-10-09 16:12:49,763] DEBUG: looking for device 'sda'... [2009-10-09 16:12:49,763] DEBUG: found DiskDevice instance (0x92caecc) -- description = name = sda status = True parents = [] kids = 2 id = 0 uuid = None format = size = 152625.344238 major = 8 minor = 0 exists = True sysfs path = /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda label = None target size = 0 path = /dev/sda format args = [] removable = False partedDevice = partedDisk = [2009-10-09 16:12:49,767] DEBUG: getFormat('None') returning DeviceFormat instance [2009-10-09 16:12:49,768] DEBUG: looking up parted Partition: /dev/sda3 [2009-10-09 16:12:49,770] DEBUG: looking up parted Device: /dev/sda3 [2009-10-09 16:12:49,778] DEBUG: added sda3 (partition) to device tree [2009-10-09 16:12:49,780] DEBUG: {'LVM2_PV_UUID': 'h6NBjv-XRr6-1fK5-4UC3-ymUf-kHA2-7BnKEl', 'ID_REVISION': '4.AA', 'LVM2_PV_SIZE': '8192000.00', 'ID_VENDOR_ENC': 'ATA\\x20\\x20\\x20\\x20\\x20', 'ID_ATA_COMPAT': 'ST3160215AS_6RAF8TR9', 'DKD_PARTITION_SIZE': '8388608000', 'ID_FS_VERSION': 'LVM2\\x20001', 'ID_PATH': 'pci-0000:00:1f.2-scsi-0:0:0:0', 'DKD_PARTITION_NUMBER': '3', 'LVM2_PE_START': '192.00', 'ID_VENDOR': 'ATA', 'LVM2_PV_NAME': '/dev/sda3', 'ID_SERIAL': 'SATA_ST3160215AS_6RAF8TR9', 'DKD_PARTITION': '1', 'MINOR': '3', 'DEVTYPE': 'partition', 'ID_FS_UUID': 'h6NBjv-XRr6-1fK5-4UC3-ymUf-kHA2-7BnKEl', 'ID_FS_UUID_ENC': 'h6NBjv-XRr6-1fK5-4UC3-ymUf-kHA2-7BnKEl', 'ID_FS_TYPE': 'LVM2_member', 'DKD_PARTITION_TYPE': '0x8e', 'ID_MODEL': 'ST3160215AS', 'MAJOR': '8', 'sysfs_path': '/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda3', 'ID_FS_USAGE': 'raid', 'ID_TYPE': 'disk', 'DKD_PARTITION_SCHEME': 'mbr', 'ID_BUS': 'scsi', 'symlinks': ['block/8:3', 'disk/by-id/scsi-SATA_ST3160215AS_6RAF8TR9-part3', 'disk/by-id/ata-ST3160215AS_6RAF8TR9-part3', 'disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part3'], 'ID_SERIAL_SHORT': '6RAF8TR9', 'name': 'sda3', 'LVM2_PV_PE_COUNT': '0', 'ANACBIN': '/sbin', 'LVM2_PV_PE_ALLOC_COUNT': '0', 'ID_MODEL_ENC': 'ST3160215AS\\x20\\x20\\x20\\x20\\x20'} [2009-10-09 16:12:49,780] DEBUG: PV sda3 has no vg_name [2009-10-09 16:12:49,780] DEBUG: PV sda3 has no vg_uuid [2009-10-09 16:12:49,780] DEBUG: type detected on 'sda3' is 'LVM2_member' [2009-10-09 16:12:49,782] DEBUG: getFormat('LVM2_member') returning LVMPhysicalVolume instance [2009-10-09 16:12:49,787] DEBUG: scanning sda4 (/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda4)... [2009-10-09 16:12:49,787] DEBUG: looking for device 'sda4'... [2009-10-09 16:12:49,788] DEBUG: found None [2009-10-09 16:12:49,788] DEBUG: sda4 is a partition [2009-10-09 16:12:49,789] DEBUG: looking for device 'sda'... [2009-10-09 16:12:49,790] DEBUG: found DiskDevice instance (0x92caecc) -- description = name = sda status = True parents = [] kids = 3 id = 0 uuid = None format = size = 152625.344238 major = 8 minor = 0 exists = True sysfs path = /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda label = None target size = 0 path = /dev/sda format args = [] removable = False partedDevice = partedDisk = [2009-10-09 16:12:49,793] DEBUG: getFormat('None') returning DeviceFormat instance [2009-10-09 16:12:49,794] DEBUG: looking up parted Partition: /dev/sda4 [2009-10-09 16:12:49,796] DEBUG: looking up parted Device: /dev/sda4 [2009-10-09 16:12:49,808] DEBUG: added sda4 (partition) to device tree [2009-10-09 16:12:49,809] DEBUG: {'ID_REVISION': '4.AA', 'DKD_PARTITION_SIZE': '135914526720', 'ID_ATA_COMPAT': 'ST3160215AS_6RAF8TR9', 'ID_PATH': 'pci-0000:00:1f.2-scsi-0:0:0:0', 'ID_VENDOR': 'ATA', 'DKD_PARTITION_NUMBER': '4', 'ID_SERIAL': 'SATA_ST3160215AS_6RAF8TR9', 'DKD_PARTITION': '1', 'DEVTYPE': 'partition', 'ID_BUS': 'scsi', 'ID_VENDOR_ENC': 'ATA\\x20\\x20\\x20\\x20\\x20', 'DKD_PARTITION_TYPE': '0x05', 'ID_MODEL': 'ST3160215AS', 'MAJOR': '8', 'sysfs_path': '/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda4', 'ID_TYPE': 'disk', 'DKD_PARTITION_SCHEME': 'mbr', 'MINOR': '4', 'symlinks': ['block/8:4', 'disk/by-id/scsi-SATA_ST3160215AS_6RAF8TR9-part4', 'disk/by-id/ata-ST3160215AS_6RAF8TR9-part4', 'disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part4'], 'ID_SERIAL_SHORT': '6RAF8TR9', 'name': 'sda4', 'ANACBIN': '/sbin', 'ID_MODEL_ENC': 'ST3160215AS\\x20\\x20\\x20\\x20\\x20'} [2009-10-09 16:12:49,809] DEBUG: no type or existing type for sda4, bailing [2009-10-09 16:12:49,810] DEBUG: scanning sda5 (/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda5)... [2009-10-09 16:12:49,811] DEBUG: looking for device 'sda5'... [2009-10-09 16:12:49,811] DEBUG: found None [2009-10-09 16:12:49,811] DEBUG: sda5 is a partition [2009-10-09 16:12:49,812] DEBUG: looking for device 'sda'... [2009-10-09 16:12:49,813] DEBUG: found DiskDevice instance (0x92caecc) -- description = name = sda status = True parents = [] kids = 4 id = 0 uuid = None format = size = 152625.344238 major = 8 minor = 0 exists = True sysfs path = /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda label = None target size = 0 path = /dev/sda format args = [] removable = False partedDevice = partedDisk = [2009-10-09 16:12:49,816] DEBUG: getFormat('None') returning DeviceFormat instance [2009-10-09 16:12:49,818] DEBUG: looking up parted Partition: /dev/sda5 [2009-10-09 16:12:49,820] DEBUG: looking up parted Device: /dev/sda5 [2009-10-09 16:12:49,828] DEBUG: added sda5 (partition) to device tree [2009-10-09 16:12:49,830] DEBUG: {'ID_REVISION': '4.AA', 'ID_VENDOR_ENC': 'ATA\\x20\\x20\\x20\\x20\\x20', 'ID_ATA_COMPAT': 'ST3160215AS_6RAF8TR9', 'DKD_PARTITION_SIZE': '8388608000', 'ID_FS_VERSION': '2', 'ID_PATH': 'pci-0000:00:1f.2-scsi-0:0:0:0', 'ID_VENDOR': 'ATA', 'DKD_PARTITION_NUMBER': '5', 'ID_SERIAL': 'SATA_ST3160215AS_6RAF8TR9', 'DKD_PARTITION': '1', 'MINOR': '5', 'DEVTYPE': 'partition', 'ID_FS_UUID': '18c20391-3fee-45ae-af9e-5bb724fa206c', 'ID_FS_UUID_ENC': '18c20391-3fee-45ae-af9e-5bb724fa206c', 'ID_FS_TYPE': 'swap', 'DKD_PARTITION_TYPE': '0x83', 'ID_MODEL': 'ST3160215AS', 'MAJOR': '8', 'sysfs_path': '/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda5', 'ID_FS_USAGE': 'other', 'ID_TYPE': 'disk', 'DKD_PARTITION_SCHEME': 'mbr', 'ID_BUS': 'scsi', 'symlinks': ['block/8:5', 'disk/by-id/scsi-SATA_ST3160215AS_6RAF8TR9-part5', 'disk/by-id/ata-ST3160215AS_6RAF8TR9-part5', 'disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part5', 'disk/by-uuid/18c20391-3fee-45ae-af9e-5bb724fa206c'], 'ID_SERIAL_SHORT': '6RAF8TR9', 'name': 'sda5', 'ANACBIN': '/sbin', 'ID_MODEL_ENC': 'ST3160215AS\\x20\\x20\\x20\\x20\\x20'} [2009-10-09 16:12:49,830] DEBUG: type detected on 'sda5' is 'swap' [2009-10-09 16:12:49,831] DEBUG: getFormat('swap') returning SwapSpace instance [2009-10-09 16:12:49,835] DEBUG: scanning sda6 (/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda6)... [2009-10-09 16:12:49,835] DEBUG: looking for device 'sda6'... [2009-10-09 16:12:49,836] DEBUG: found None [2009-10-09 16:12:49,836] DEBUG: sda6 is a partition [2009-10-09 16:12:49,837] DEBUG: looking for device 'sda'... [2009-10-09 16:12:49,838] DEBUG: found DiskDevice instance (0x92caecc) -- description = name = sda status = True parents = [] kids = 5 id = 0 uuid = None format = size = 152625.344238 major = 8 minor = 0 exists = True sysfs path = /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda label = None target size = 0 path = /dev/sda format args = [] removable = False partedDevice = partedDisk = [2009-10-09 16:12:49,841] DEBUG: getFormat('None') returning DeviceFormat instance [2009-10-09 16:12:49,842] DEBUG: looking up parted Partition: /dev/sda6 [2009-10-09 16:12:49,844] DEBUG: looking up parted Device: /dev/sda6 [2009-10-09 16:12:49,852] DEBUG: added sda6 (partition) to device tree [2009-10-09 16:12:49,854] DEBUG: {'ID_REVISION': '4.AA', 'ID_VENDOR_ENC': 'ATA\\x20\\x20\\x20\\x20\\x20', 'ID_ATA_COMPAT': 'ST3160215AS_6RAF8TR9', 'DKD_PARTITION_SIZE': '5242879488', 'ID_FS_VERSION': '1.0', 'ID_PATH': 'pci-0000:00:1f.2-scsi-0:0:0:0', 'ID_VENDOR': 'ATA', 'DKD_PARTITION_NUMBER': '6', 'ID_SERIAL': 'SATA_ST3160215AS_6RAF8TR9', 'DKD_PARTITION': '1', 'MINOR': '6', 'DEVTYPE': 'partition', 'ID_FS_UUID': '06b3af73-3a68-4831-abaa-7cb6dbc65f2d', 'ID_FS_UUID_ENC': '06b3af73-3a68-4831-abaa-7cb6dbc65f2d', 'ID_FS_TYPE': 'ext4', 'DKD_PARTITION_TYPE': '0x83', 'ID_MODEL': 'ST3160215AS', 'MAJOR': '8', 'sysfs_path': '/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda6', 'ID_FS_USAGE': 'filesystem', 'ID_TYPE': 'disk', 'DKD_PARTITION_SCHEME': 'mbr', 'ID_BUS': 'scsi', 'symlinks': ['block/8:6', 'disk/by-id/scsi-SATA_ST3160215AS_6RAF8TR9-part6', 'disk/by-id/ata-ST3160215AS_6RAF8TR9-part6', 'disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part6', 'disk/by-uuid/06b3af73-3a68-4831-abaa-7cb6dbc65f2d'], 'ID_SERIAL_SHORT': '6RAF8TR9', 'name': 'sda6', 'ANACBIN': '/sbin', 'ID_MODEL_ENC': 'ST3160215AS\\x20\\x20\\x20\\x20\\x20'} [2009-10-09 16:12:49,854] DEBUG: type detected on 'sda6' is 'ext4' [2009-10-09 16:12:49,958] DEBUG: getFormat('ext4') returning Ext4FS instance [2009-10-09 16:12:49,967] DEBUG: scanning sda7 (/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda7)... [2009-10-09 16:12:49,968] DEBUG: looking for device 'sda7'... [2009-10-09 16:12:49,968] DEBUG: found None [2009-10-09 16:12:49,968] DEBUG: sda7 is a partition [2009-10-09 16:12:49,969] DEBUG: looking for device 'sda'... [2009-10-09 16:12:49,970] DEBUG: found DiskDevice instance (0x92caecc) -- description = name = sda status = True parents = [] kids = 6 id = 0 uuid = None format = size = 152625.344238 major = 8 minor = 0 exists = True sysfs path = /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda label = None target size = 0 path = /dev/sda format args = [] removable = False partedDevice = partedDisk = [2009-10-09 16:12:49,973] DEBUG: getFormat('None') returning DeviceFormat instance [2009-10-09 16:12:49,975] DEBUG: looking up parted Partition: /dev/sda7 [2009-10-09 16:12:49,977] DEBUG: looking up parted Device: /dev/sda7 [2009-10-09 16:12:49,985] DEBUG: added sda7 (partition) to device tree [2009-10-09 16:12:49,987] DEBUG: {'ID_REVISION': '4.AA', 'ID_VENDOR_ENC': 'ATA\\x20\\x20\\x20\\x20\\x20', 'ID_ATA_COMPAT': 'ST3160215AS_6RAF8TR9', 'DKD_PARTITION_SIZE': '5242879488', 'ID_FS_VERSION': '1.0', 'ID_PATH': 'pci-0000:00:1f.2-scsi-0:0:0:0', 'ID_VENDOR': 'ATA', 'DKD_PARTITION_NUMBER': '7', 'ID_SERIAL': 'SATA_ST3160215AS_6RAF8TR9', 'DKD_PARTITION': '1', 'MINOR': '7', 'DEVTYPE': 'partition', 'ID_FS_UUID': '8a891d79-6cfe-451e-a823-1de04308919a', 'ID_FS_UUID_ENC': '8a891d79-6cfe-451e-a823-1de04308919a', 'ID_FS_TYPE': 'ext4', 'DKD_PARTITION_TYPE': '0x83', 'ID_MODEL': 'ST3160215AS', 'MAJOR': '8', 'sysfs_path': '/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda7', 'ID_FS_USAGE': 'filesystem', 'ID_TYPE': 'disk', 'DKD_PARTITION_SCHEME': 'mbr', 'ID_BUS': 'scsi', 'symlinks': ['block/8:7', 'disk/by-id/scsi-SATA_ST3160215AS_6RAF8TR9-part7', 'disk/by-id/ata-ST3160215AS_6RAF8TR9-part7', 'disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part7', 'disk/by-uuid/8a891d79-6cfe-451e-a823-1de04308919a'], 'ID_SERIAL_SHORT': '6RAF8TR9', 'name': 'sda7', 'ANACBIN': '/sbin', 'ID_MODEL_ENC': 'ST3160215AS\\x20\\x20\\x20\\x20\\x20'} [2009-10-09 16:12:49,987] DEBUG: type detected on 'sda7' is 'ext4' [2009-10-09 16:12:50,177] DEBUG: getFormat('ext4') returning Ext4FS instance [2009-10-09 16:12:50,186] DEBUG: scanning sda8 (/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda8)... [2009-10-09 16:12:50,186] DEBUG: looking for device 'sda8'... [2009-10-09 16:12:50,187] DEBUG: found None [2009-10-09 16:12:50,187] DEBUG: sda8 is a partition [2009-10-09 16:12:50,190] DEBUG: looking for device 'sda'... [2009-10-09 16:12:50,191] DEBUG: found DiskDevice instance (0x92caecc) -- description = name = sda status = True parents = [] kids = 7 id = 0 uuid = None format = size = 152625.344238 major = 8 minor = 0 exists = True sysfs path = /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda label = None target size = 0 path = /dev/sda format args = [] removable = False partedDevice = partedDisk = [2009-10-09 16:12:50,198] DEBUG: getFormat('None') returning DeviceFormat instance [2009-10-09 16:12:50,201] DEBUG: looking up parted Partition: /dev/sda8 [2009-10-09 16:12:50,205] DEBUG: looking up parted Device: /dev/sda8 [2009-10-09 16:12:50,215] DEBUG: added sda8 (partition) to device tree [2009-10-09 16:12:50,216] DEBUG: {'ID_REVISION': '4.AA', 'ID_VENDOR_ENC': 'ATA\\x20\\x20\\x20\\x20\\x20', 'ID_ATA_COMPAT': 'ST3160215AS_6RAF8TR9', 'DKD_PARTITION_SIZE': '5242879488', 'ID_FS_VERSION': '1.0', 'ID_PATH': 'pci-0000:00:1f.2-scsi-0:0:0:0', 'ID_VENDOR': 'ATA', 'DKD_PARTITION_NUMBER': '8', 'ID_SERIAL': 'SATA_ST3160215AS_6RAF8TR9', 'DKD_PARTITION': '1', 'MINOR': '8', 'DEVTYPE': 'partition', 'ID_FS_UUID': '9f73e989-7e77-4e53-8896-4053929ee4b8', 'ID_FS_UUID_ENC': '9f73e989-7e77-4e53-8896-4053929ee4b8', 'ID_FS_TYPE': 'ext4', 'DKD_PARTITION_TYPE': '0x83', 'ID_MODEL': 'ST3160215AS', 'MAJOR': '8', 'sysfs_path': '/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda8', 'ID_FS_USAGE': 'filesystem', 'ID_TYPE': 'disk', 'DKD_PARTITION_SCHEME': 'mbr', 'ID_BUS': 'scsi', 'symlinks': ['block/8:8', 'disk/by-id/scsi-SATA_ST3160215AS_6RAF8TR9-part8', 'disk/by-id/ata-ST3160215AS_6RAF8TR9-part8', 'disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part8', 'disk/by-uuid/9f73e989-7e77-4e53-8896-4053929ee4b8'], 'ID_SERIAL_SHORT': '6RAF8TR9', 'name': 'sda8', 'ANACBIN': '/sbin', 'ID_MODEL_ENC': 'ST3160215AS\\x20\\x20\\x20\\x20\\x20'} [2009-10-09 16:12:50,216] DEBUG: type detected on 'sda8' is 'ext4' [2009-10-09 16:12:50,274] DEBUG: getFormat('ext4') returning Ext4FS instance [2009-10-09 16:12:50,282] DEBUG: scanning sda9 (/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda9)... [2009-10-09 16:12:50,283] DEBUG: looking for device 'sda9'... [2009-10-09 16:12:50,283] DEBUG: found None [2009-10-09 16:12:50,284] DEBUG: sda9 is a partition [2009-10-09 16:12:50,286] DEBUG: looking for device 'sda'... [2009-10-09 16:12:50,287] DEBUG: found DiskDevice instance (0x92caecc) -- description = name = sda status = True parents = [] kids = 8 id = 0 uuid = None format = size = 152625.344238 major = 8 minor = 0 exists = True sysfs path = /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda label = None target size = 0 path = /dev/sda format args = [] removable = False partedDevice = partedDisk = [2009-10-09 16:12:50,290] DEBUG: getFormat('None') returning DeviceFormat instance [2009-10-09 16:12:50,292] DEBUG: looking up parted Partition: /dev/sda9 [2009-10-09 16:12:50,294] DEBUG: looking up parted Device: /dev/sda9 [2009-10-09 16:12:50,303] DEBUG: added sda9 (partition) to device tree [2009-10-09 16:12:50,305] DEBUG: {'ID_REVISION': '4.AA', 'DKD_PARTITION_SIZE': '5242879488', 'ID_ATA_COMPAT': 'ST3160215AS_6RAF8TR9', 'ID_PATH': 'pci-0000:00:1f.2-scsi-0:0:0:0', 'ID_VENDOR': 'ATA', 'DKD_PARTITION_NUMBER': '9', 'ID_SERIAL': 'SATA_ST3160215AS_6RAF8TR9', 'DKD_PARTITION': '1', 'DEVTYPE': 'partition', 'ID_BUS': 'scsi', 'ID_VENDOR_ENC': 'ATA\\x20\\x20\\x20\\x20\\x20', 'DKD_PARTITION_TYPE': '0x83', 'ID_MODEL': 'ST3160215AS', 'MAJOR': '8', 'sysfs_path': '/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda9', 'ID_TYPE': 'disk', 'DKD_PARTITION_SCHEME': 'mbr', 'MINOR': '9', 'symlinks': ['block/8:9', 'disk/by-id/scsi-SATA_ST3160215AS_6RAF8TR9-part9', 'disk/by-id/ata-ST3160215AS_6RAF8TR9-part9', 'disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part9'], 'ID_SERIAL_SHORT': '6RAF8TR9', 'name': 'sda9', 'ANACBIN': '/sbin', 'ID_MODEL_ENC': 'ST3160215AS\\x20\\x20\\x20\\x20\\x20'} [2009-10-09 16:12:50,305] DEBUG: no type or existing type for sda9, bailing [2009-10-09 16:12:50,306] DEBUG: scanning sda10 (/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda10)... [2009-10-09 16:12:50,306] DEBUG: looking for device 'sda10'... [2009-10-09 16:12:50,306] DEBUG: found None [2009-10-09 16:12:50,307] DEBUG: sda10 is a partition [2009-10-09 16:12:50,308] DEBUG: looking for device 'sda'... [2009-10-09 16:12:50,308] DEBUG: found DiskDevice instance (0x92caecc) -- description = name = sda status = True parents = [] kids = 9 id = 0 uuid = None format = size = 152625.344238 major = 8 minor = 0 exists = True sysfs path = /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda label = None target size = 0 path = /dev/sda format args = [] removable = False partedDevice = partedDisk = [2009-10-09 16:12:50,312] DEBUG: getFormat('None') returning DeviceFormat instance [2009-10-09 16:12:50,313] DEBUG: looking up parted Partition: /dev/sda10 [2009-10-09 16:12:50,315] DEBUG: looking up parted Device: /dev/sda10 [2009-10-09 16:12:50,325] DEBUG: added sda10 (partition) to device tree [2009-10-09 16:12:50,327] DEBUG: {'ID_REVISION': '4.AA', 'ID_VENDOR_ENC': 'ATA\\x20\\x20\\x20\\x20\\x20', 'ID_ATA_COMPAT': 'ST3160215AS_6RAF8TR9', 'DKD_PARTITION_SIZE': '209714688', 'ID_FS_VERSION': '1.0', 'ID_PATH': 'pci-0000:00:1f.2-scsi-0:0:0:0', 'ID_VENDOR': 'ATA', 'DKD_PARTITION_NUMBER': '10', 'ID_SERIAL': 'SATA_ST3160215AS_6RAF8TR9', 'DKD_PARTITION': '1', 'MINOR': '10', 'DEVTYPE': 'partition', 'ID_FS_UUID': '2d189a9c-eb0e-49b0-a9d3-1dc36acd61eb', 'ID_FS_UUID_ENC': '2d189a9c-eb0e-49b0-a9d3-1dc36acd61eb', 'ID_FS_TYPE': 'ext3', 'DKD_PARTITION_TYPE': '0x83', 'ID_MODEL': 'ST3160215AS', 'MAJOR': '8', 'sysfs_path': '/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda10', 'ID_FS_USAGE': 'filesystem', 'ID_TYPE': 'disk', 'DKD_PARTITION_SCHEME': 'mbr', 'ID_BUS': 'scsi', 'symlinks': ['block/8:10', 'disk/by-id/scsi-SATA_ST3160215AS_6RAF8TR9-part10', 'disk/by-id/ata-ST3160215AS_6RAF8TR9-part10', 'disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part10', 'disk/by-uuid/2d189a9c-eb0e-49b0-a9d3-1dc36acd61eb'], 'ID_SERIAL_SHORT': '6RAF8TR9', 'name': 'sda10', 'ANACBIN': '/sbin', 'ID_MODEL_ENC': 'ST3160215AS\\x20\\x20\\x20\\x20\\x20'} [2009-10-09 16:12:50,327] DEBUG: type detected on 'sda10' is 'ext3' [2009-10-09 16:12:50,447] DEBUG: getFormat('ext3') returning Ext3FS instance [2009-10-09 16:12:50,463] DEBUG: scanning sda11 (/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda11)... [2009-10-09 16:12:50,463] DEBUG: looking for device 'sda11'... [2009-10-09 16:12:50,464] DEBUG: found None [2009-10-09 16:12:50,464] DEBUG: sda11 is a partition [2009-10-09 16:12:50,467] DEBUG: looking for device 'sda'... [2009-10-09 16:12:50,468] DEBUG: found DiskDevice instance (0x92caecc) -- description = name = sda status = True parents = [] kids = 10 id = 0 uuid = None format = size = 152625.344238 major = 8 minor = 0 exists = True sysfs path = /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda label = None target size = 0 path = /dev/sda format args = [] removable = False partedDevice = partedDisk = [2009-10-09 16:12:50,474] DEBUG: getFormat('None') returning DeviceFormat instance [2009-10-09 16:12:50,476] DEBUG: looking up parted Partition: /dev/sda11 [2009-10-09 16:12:50,478] DEBUG: looking up parted Device: /dev/sda11 [2009-10-09 16:12:50,490] DEBUG: added sda11 (partition) to device tree [2009-10-09 16:12:50,493] DEBUG: {'DKD_PARTITION_NUMBER': '11', 'LVM2_PV_UUID': '6OVn42-iGEo-d0qW-V86L-7b4B-2qsv-shCcjK', 'LVM2_VG_EXTENT_SIZE': '4096.00', 'ID_REVISION': '4.AA', 'LVM2_PV_SIZE': '103849984.00', 'ID_VENDOR_ENC': 'ATA\\x20\\x20\\x20\\x20\\x20', 'ID_ATA_COMPAT': 'ST3160215AS_6RAF8TR9', 'DKD_PARTITION_SIZE': '106344480256', 'ID_FS_VERSION': 'LVM2\\x20001', 'ID_PATH': 'pci-0000:00:1f.2-scsi-0:0:0:0', 'LVM2_VG_UUID': '1SLacE-6k11-Q6BT-rfKJ-vo7J-OOW8-Xz2ZGh', 'LVM2_LV_SIZE': '101785600.00', 'LVM2_PE_START': '192.00', 'ID_VENDOR': 'ATA', 'LVM2_PV_NAME': '/dev/sda11', 'ID_SERIAL': 'SATA_ST3160215AS_6RAF8TR9', 'DKD_PARTITION': '1', 'DEVTYPE': 'partition', 'MINOR': '11', 'LVM2_LV_NAME': 'lv_root', 'ID_FS_UUID': '6OVn42-iGEo-d0qW-V86L-7b4B-2qsv-shCcjK', 'LVM2_PV_COUNT': '1', 'ID_FS_UUID_ENC': '6OVn42-iGEo-d0qW-V86L-7b4B-2qsv-shCcjK', 'ID_FS_TYPE': 'LVM2_member', 'LVM2_LV_UUID': '32BGjo-3Xmn-jI0r-oyRP-2RkI-0JE6-RK7M7G', 'LVM2_VG_FREE_COUNT': '504', 'DKD_PARTITION_TYPE': '0x8e', 'ID_MODEL': 'ST3160215AS', 'LVM2_VG_EXTENT_COUNT': '25354', 'MAJOR': '8', 'sysfs_path': '/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda11', 'ID_FS_USAGE': 'raid', 'ID_TYPE': 'disk', 'LVM2_VG_NAME': 'VolGroup', 'DKD_PARTITION_SCHEME': 'mbr', 'LVM2_VG_FREE': '2064384.00', 'ID_BUS': 'scsi', 'symlinks': ['block/8:11', 'disk/by-id/scsi-SATA_ST3160215AS_6RAF8TR9-part11', 'disk/by-id/ata-ST3160215AS_6RAF8TR9-part11', 'disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part11'], 'ID_SERIAL_SHORT': '6RAF8TR9', 'name': 'sda11', 'LVM2_PV_PE_COUNT': '25354', 'ANACBIN': '/sbin', 'LVM2_PV_PE_ALLOC_COUNT': '24850', 'ID_MODEL_ENC': 'ST3160215AS\\x20\\x20\\x20\\x20\\x20', 'LVM2_VG_SIZE': '103849984.00'} [2009-10-09 16:12:50,494] DEBUG: type detected on 'sda11' is 'LVM2_member' [2009-10-09 16:12:50,497] DEBUG: getFormat('LVM2_member') returning LVMPhysicalVolume instance [2009-10-09 16:12:50,505] DEBUG: looking for device 'VolGroup'... [2009-10-09 16:12:50,506] DEBUG: found None [2009-10-09 16:12:50,510] DEBUG: getFormat('None') returning DeviceFormat instance [2009-10-09 16:12:50,514] DEBUG: added VolGroup (lvmvg) to device tree [2009-10-09 16:12:50,514] DEBUG: looking for device 'VolGroup-lv_root'... [2009-10-09 16:12:50,514] DEBUG: found None [2009-10-09 16:12:50,518] DEBUG: getFormat('None') returning DeviceFormat instance [2009-10-09 16:12:50,522] DEBUG: added VolGroup-lv_root (lvmlv) to device tree [2009-10-09 16:12:51,365] DEBUG: looking up parted Device: /dev/mapper/VolGroup-lv_root [2009-10-09 16:12:51,368] DEBUG: scanning live-rw (/devices/virtual/block/dm-0)... [2009-10-09 16:12:51,369] DEBUG: looking for device 'live-rw'... [2009-10-09 16:12:51,369] DEBUG: found None [2009-10-09 16:12:51,370] DEBUG: live-rw is a device-mapper device [2009-10-09 16:12:51,387] DEBUG: failed to find dm node for VolGroup [2009-10-09 16:12:51,388] DEBUG: looking for device 'loop3'... [2009-10-09 16:12:51,388] DEBUG: found None [2009-10-09 16:12:51,392] DEBUG: ignoring loop3 (/devices/virtual/block/loop3) [2009-10-09 16:12:51,393] DEBUG: looking for device 'loop3'... [2009-10-09 16:12:51,394] DEBUG: found None [2009-10-09 16:12:51,394] ERROR: failure scanning device live-rw: could not add slave loop3 [2009-10-09 16:12:51,397] DEBUG: {'ID_FS_VERSION': '1.0', 'DKD_DM_TARGET_COUNT': '1', 'DM_OPEN': '1', 'DM_MINOR': '0', 'DM_NAME': 'live-rw', 'ID_FS_LABEL_ENC': 'Fedora-11-i686-L', 'ANACBIN': '/sbin', 'DKD_DM_TARGET_TYPES': 'snapshot', 'DKD_DM_LAST_EVENT_NR': '0', 'DEVTYPE': 'disk', 'DM_SUSPENDED': 'Active', 'DKD_DM_NAME': 'live-rw', 'DKD_DM_MAJOR': '253', 'ID_FS_UUID': 'd8394cd3-060a-42c8-8585-aebb23927bcb', 'ID_FS_UUID_ENC': 'd8394cd3-060a-42c8-8585-aebb23927bcb', 'ID_FS_TYPE': 'ext4', 'DM_MAJOR': '253', 'DKD_DM_OPENCOUNT': '1', 'sysfs_path': '/devices/virtual/block/dm-0', 'ID_FS_LABEL': 'Fedora-11-i686-L', 'ID_FS_USAGE': 'filesystem', 'DM_READONLY': 'Writeable', 'DKD_DM_TABLE_STATE': 'LIVE', 'MINOR': '0', 'symlinks': ['block/253:0', 'disk/by-id/dm-name-live-rw', 'disk/by-uuid/d8394cd3-060a-42c8-8585-aebb23927bcb', 'disk/by-label/Fedora-11-i686-L'], 'DM_TABLES_LOADED': 'Live', 'MAJOR': '253', 'name': 'dm-0', 'DKD_DM_MINOR': '0', 'DKD_DM_STATE': 'ACTIVE', 'DKD_MEDIA_AVAILABLE': '1'} [2009-10-09 16:12:51,397] DEBUG: no type or existing type for live-rw, bailing [2009-10-09 16:12:51,400] DEBUG: scanning live-osimg-min (/devices/virtual/block/dm-1)... [2009-10-09 16:12:51,400] DEBUG: looking for device 'live-osimg-min'... [2009-10-09 16:12:51,401] DEBUG: found None [2009-10-09 16:12:51,401] DEBUG: live-osimg-min is a device-mapper device [2009-10-09 16:12:51,415] DEBUG: failed to find dm node for VolGroup [2009-10-09 16:12:51,416] DEBUG: looking for device 'loop3'... [2009-10-09 16:12:51,416] DEBUG: found None [2009-10-09 16:12:51,418] DEBUG: ignoring loop3 (/devices/virtual/block/loop3) [2009-10-09 16:12:51,418] DEBUG: looking for device 'loop3'... [2009-10-09 16:12:51,418] DEBUG: found None [2009-10-09 16:12:51,418] ERROR: failure scanning device live-osimg-min: could not add slave loop3 [2009-10-09 16:12:51,420] DEBUG: {'ID_FS_VERSION': '1.0', 'DKD_DM_TARGET_COUNT': '1', 'DM_OPEN': '0', 'DM_MINOR': '1', 'DM_NAME': 'live-osimg-min', 'ID_FS_LABEL_ENC': 'Fedora-11-i686-L', 'ANACBIN': '/sbin', 'DKD_DM_TARGET_TYPES': 'snapshot', 'DKD_DM_LAST_EVENT_NR': '0', 'DEVTYPE': 'disk', 'DM_SUSPENDED': 'Active', 'DKD_DM_NAME': 'live-osimg-min', 'DKD_DM_MAJOR': '253', 'ID_FS_UUID': 'd8394cd3-060a-42c8-8585-aebb23927bcb', 'ID_FS_UUID_ENC': 'd8394cd3-060a-42c8-8585-aebb23927bcb', 'ID_FS_TYPE': 'ext4', 'DM_MAJOR': '253', 'DKD_DM_OPENCOUNT': '0', 'sysfs_path': '/devices/virtual/block/dm-1', 'ID_FS_LABEL': 'Fedora-11-i686-L', 'ID_FS_USAGE': 'filesystem', 'DM_READONLY': 'Read-only', 'DKD_DM_TABLE_STATE': 'LIVE', 'MINOR': '1', 'symlinks': ['block/253:1', 'disk/by-id/dm-name-live-osimg-min', 'disk/by-uuid/d8394cd3-060a-42c8-8585-aebb23927bcb', 'disk/by-label/Fedora-11-i686-L'], 'DM_TABLES_LOADED': 'Live', 'MAJOR': '253', 'name': 'dm-1', 'DKD_DM_MINOR': '1', 'DKD_DM_STATE': 'READONLY', 'DKD_MEDIA_AVAILABLE': '1'} [2009-10-09 16:12:51,420] DEBUG: no type or existing type for live-osimg-min, bailing [2009-10-09 16:12:53,094] INFO: sr0 looks to be the live device; ignoring [2009-10-09 16:12:53,102] INFO: devices to scan: ['dm-2'] [2009-10-09 16:12:53,105] DEBUG: scanning VolGroup-lv_root (/devices/virtual/block/dm-2)... [2009-10-09 16:12:53,105] DEBUG: looking for device 'VolGroup-lv_root'... [2009-10-09 16:12:53,106] DEBUG: found LVMLogicalVolumeDevice instance (0x94b3f6c) -- description = name = VolGroup-lv_root status = True parents = [] kids = 0 id = 13 uuid = 32BGjo-3Xmn-jI0r-oyRP-2RkI-0JE6-RK7M7G format = size = 99400.0 major = 0 minor = 0 exists = True sysfs path = label = None target size = 99400.0 path = /dev/mapper/VolGroup-lv_root format args = [] target = None dmUuid = None VG device = percent = 0 [2009-10-09 16:12:53,107] DEBUG: VolGroup-lv_root is a device-mapper device [2009-10-09 16:12:53,109] DEBUG: {'ID_FS_VERSION': '1.0', 'DKD_DM_TARGET_COUNT': '1', 'DM_OPEN': '0', 'DM_MINOR': '2', 'DM_NAME': 'VolGroup-lv_root', 'ANACBIN': '/sbin', 'DKD_DM_TARGET_TYPES': 'linear', 'DKD_DM_LAST_EVENT_NR': '0', 'DEVTYPE': 'disk', 'DM_SUSPENDED': 'Active', 'DKD_DM_NAME': 'VolGroup-lv_root', 'DKD_DM_MAJOR': '253', 'ID_FS_UUID': '5e1620a1-9533-4021-b0bc-145d9276d807', 'ID_FS_UUID_ENC': '5e1620a1-9533-4021-b0bc-145d9276d807', 'ID_FS_TYPE': 'ext4', 'DKD_DM_UUID': 'LVM-1SLacE6k11Q6BTrfKJvo7JOOW8Xz2ZGh32BGjo3XmnjI0royRP2RkI0JE6RK7M7G', 'DM_MAJOR': '253', 'DKD_DM_OPENCOUNT': '0', 'DM_UUID': 'LVM-1SLacE6k11Q6BTrfKJvo7JOOW8Xz2ZGh32BGjo3XmnjI0royRP2RkI0JE6RK7M7G', 'sysfs_path': '/devices/virtual/block/dm-2', 'DKD_DM_STATE': 'ACTIVE', 'ID_FS_USAGE': 'filesystem', 'DM_READONLY': 'Writeable', 'DKD_DM_TABLE_STATE': 'LIVE', 'MINOR': '2', 'symlinks': ['block/253:2', 'disk/by-id/dm-name-VolGroup-lv_root', 'disk/by-id/dm-uuid-LVM-1SLacE6k11Q6BTrfKJvo7JOOW8Xz2ZGh32BGjo3XmnjI0royRP2RkI0JE6RK7M7G', 'disk/by-uuid/5e1620a1-9533-4021-b0bc-145d9276d807'], 'DM_TABLES_LOADED': 'Live', 'MAJOR': '253', 'name': 'dm-2', 'DKD_DM_MINOR': '2', 'DKD_MEDIA_AVAILABLE': '1'} [2009-10-09 16:12:53,110] DEBUG: type detected on 'VolGroup-lv_root' is 'ext4' [2009-10-09 16:12:53,159] DEBUG: getFormat('ext4') returning Ext4FS instance [2009-10-09 16:12:53,191] INFO: sr0 looks to be the live device; ignoring [2009-10-09 16:12:57,287] INFO: failed to unlink /etc/mdadm.conf [2009-10-09 21:43:39,925] DEBUG: doAutoPartition(<__main__.Anaconda instance at 0x87cf84c>) [2009-10-09 21:43:39,925] DEBUG: doAutoPart: True [2009-10-09 21:43:39,925] DEBUG: clearPartType: 1 [2009-10-09 21:43:39,926] DEBUG: clearPartDisks: ['sda'] [2009-10-09 21:43:39,926] DEBUG: autoPartitionRequests: [, , ] [2009-10-09 21:43:39,926] DEBUG: storage.disks: [] [2009-10-09 21:43:39,927] DEBUG: all names: ['VolGroup-lv_root', 'sda7', 'sda10', 'sda11', 'VolGroup', 'sda8', 'sda9', 'sda4', 'sda5', 'sda6', 'sda', 'sda1', 'sda2', 'sda3'] [2009-10-09 21:43:39,927] DEBUG: clearpart: looking at sda1 [2009-10-09 21:43:39,928] DEBUG: clearing sda1 [2009-10-09 21:43:39,929] DEBUG: partitions: ['sda1', 'sda2', 'sda3', 'sda4', 'sda5', 'sda6', 'sda7', 'sda8', 'sda9', 'sda10', 'sda11'] [2009-10-09 21:43:39,929] DEBUG: clearpart: looking at sda10 [2009-10-09 21:43:39,929] DEBUG: clearing sda10 [2009-10-09 21:43:39,930] DEBUG: partitions: ['sda1', 'sda2', 'sda3', 'sda4', 'sda5', 'sda6', 'sda7', 'sda8', 'sda9', 'sda10', 'sda11'] [2009-10-09 21:43:39,931] DEBUG: clearpart: looking at sda11 [2009-10-09 21:43:39,931] DEBUG: clearing sda11 [2009-10-09 21:43:39,932] DEBUG: devices to remove: ['VolGroup-lv_root', 'VolGroup'] [2009-10-09 21:43:39,932] DEBUG: leaves to remove: ['VolGroup-lv_root'] [2009-10-09 21:43:39,935] DEBUG: getFormat('None') returning DeviceFormat instance [2009-10-09 21:43:39,939] DEBUG: registered action: Destroy Format None on VolGroup-lv_root (lvmlv) [2009-10-09 21:43:39,942] DEBUG: removed VolGroup-lv_root (lvmlv) from device tree [2009-10-09 21:43:39,945] DEBUG: registered action: Destroy Device VolGroup-lv_root (lvmlv) [2009-10-09 21:43:39,945] DEBUG: devices to remove: ['VolGroup'] [2009-10-09 21:43:39,946] DEBUG: leaves to remove: ['VolGroup'] [2009-10-09 21:43:40,072] DEBUG: removed VolGroup (lvmvg) from device tree [2009-10-09 21:43:40,075] DEBUG: registered action: Destroy Device VolGroup (lvmvg) [2009-10-09 21:43:40,076] DEBUG: partitions: ['sda1', 'sda2', 'sda3', 'sda4', 'sda5', 'sda6', 'sda7', 'sda8', 'sda9', 'sda10', 'sda11'] [2009-10-09 21:43:40,076] DEBUG: clearpart: looking at sda2 [2009-10-09 21:43:40,077] DEBUG: clearing sda2 [2009-10-09 21:43:40,078] DEBUG: partitions: ['sda1', 'sda2', 'sda3', 'sda4', 'sda5', 'sda6', 'sda7', 'sda8', 'sda9', 'sda10', 'sda11'] [2009-10-09 21:43:40,078] DEBUG: clearpart: looking at sda3 [2009-10-09 21:43:40,078] DEBUG: clearing sda3 [2009-10-09 21:43:40,079] DEBUG: partitions: ['sda1', 'sda2', 'sda3', 'sda4', 'sda5', 'sda6', 'sda7', 'sda8', 'sda9', 'sda10', 'sda11'] [2009-10-09 21:43:40,080] DEBUG: clearpart: looking at sda4 [2009-10-09 21:43:40,080] DEBUG: clearpart: looking at sda5 [2009-10-09 21:43:40,080] DEBUG: clearing sda5 [2009-10-09 21:43:40,081] DEBUG: partitions: ['sda1', 'sda2', 'sda3', 'sda4', 'sda5', 'sda6', 'sda7', 'sda8', 'sda9', 'sda10', 'sda11'] [2009-10-09 21:43:40,082] DEBUG: clearpart: looking at sda6 [2009-10-09 21:43:40,082] DEBUG: clearing sda6 [2009-10-09 21:43:40,083] DEBUG: partitions: ['sda1', 'sda2', 'sda3', 'sda4', 'sda5', 'sda6', 'sda7', 'sda8', 'sda9', 'sda10', 'sda11'] [2009-10-09 21:43:40,083] DEBUG: clearpart: looking at sda7 [2009-10-09 21:43:40,084] DEBUG: clearing sda7 [2009-10-09 21:43:40,085] DEBUG: partitions: ['sda1', 'sda2', 'sda3', 'sda4', 'sda5', 'sda6', 'sda7', 'sda8', 'sda9', 'sda10', 'sda11'] [2009-10-09 21:43:40,085] DEBUG: clearpart: looking at sda8 [2009-10-09 21:43:40,085] DEBUG: clearing sda8 [2009-10-09 21:43:40,086] DEBUG: partitions: ['sda1', 'sda2', 'sda3', 'sda4', 'sda5', 'sda6', 'sda7', 'sda8', 'sda9', 'sda10', 'sda11'] [2009-10-09 21:43:40,086] DEBUG: clearpart: looking at sda9 [2009-10-09 21:43:40,087] DEBUG: clearing sda9 [2009-10-09 21:43:40,088] DEBUG: partitions: ['sda1', 'sda2', 'sda3', 'sda4', 'sda5', 'sda6', 'sda7', 'sda8', 'sda9', 'sda10', 'sda11'] [2009-10-09 21:43:40,091] DEBUG: getFormat('None') returning DeviceFormat instance [2009-10-09 21:43:40,093] DEBUG: registered action: Destroy Format None on sda1 (partition) [2009-10-09 21:43:40,110] DEBUG: removed sda1 (partition) from device tree [2009-10-09 21:43:40,112] DEBUG: registered action: Destroy Device sda1 (partition) [2009-10-09 21:43:40,114] DEBUG: getFormat('None') returning DeviceFormat instance [2009-10-09 21:43:40,115] DEBUG: registered action: Destroy Format None on sda10 (partition) [2009-10-09 21:43:40,136] DEBUG: removed sda10 (partition) from device tree [2009-10-09 21:43:40,139] DEBUG: registered action: Destroy Device sda10 (partition) [2009-10-09 21:43:40,146] DEBUG: getFormat('None') returning DeviceFormat instance [2009-10-09 21:43:40,149] DEBUG: registered action: Destroy Format None on sda10 (partition) [2009-10-09 21:43:40,183] DEBUG: removed sda10 (partition) from device tree [2009-10-09 21:43:40,186] DEBUG: registered action: Destroy Device sda10 (partition) [2009-10-09 21:43:40,207] DEBUG: removed sda2 (partition) from device tree [2009-10-09 21:43:40,208] DEBUG: registered action: Destroy Device sda2 (partition) [2009-10-09 21:43:40,212] DEBUG: getFormat('None') returning DeviceFormat instance [2009-10-09 21:43:40,213] DEBUG: registered action: Destroy Format None on sda3 (partition) [2009-10-09 21:43:40,237] DEBUG: removed sda3 (partition) from device tree [2009-10-09 21:43:40,240] DEBUG: registered action: Destroy Device sda3 (partition) [2009-10-09 21:43:40,245] DEBUG: getFormat('None') returning DeviceFormat instance [2009-10-09 21:43:40,248] DEBUG: registered action: Destroy Format None on sda5 (partition) [2009-10-09 21:43:40,266] DEBUG: removed sda5 (partition) from device tree [2009-10-09 21:43:40,268] DEBUG: registered action: Destroy Device sda5 (partition) [2009-10-09 21:43:40,270] DEBUG: getFormat('None') returning DeviceFormat instance [2009-10-09 21:43:40,271] DEBUG: registered action: Destroy Format None on sda5 (partition) [2009-10-09 21:43:40,289] DEBUG: removed sda5 (partition) from device tree [2009-10-09 21:43:40,290] DEBUG: registered action: Destroy Device sda5 (partition) [2009-10-09 21:43:40,293] DEBUG: getFormat('None') returning DeviceFormat instance [2009-10-09 21:43:40,294] DEBUG: registered action: Destroy Format None on sda5 (partition) [2009-10-09 21:43:40,311] DEBUG: removed sda5 (partition) from device tree [2009-10-09 21:43:40,313] DEBUG: registered action: Destroy Device sda5 (partition) [2009-10-09 21:43:40,315] DEBUG: getFormat('None') returning DeviceFormat instance [2009-10-09 21:43:40,317] DEBUG: registered action: Destroy Format None on sda5 (partition) [2009-10-09 21:43:40,334] DEBUG: removed sda5 (partition) from device tree [2009-10-09 21:43:40,336] DEBUG: registered action: Destroy Device sda5 (partition) [2009-10-09 21:43:40,353] DEBUG: removed sda5 (partition) from device tree [2009-10-09 21:43:40,355] DEBUG: registered action: Destroy Device sda5 (partition) [2009-10-09 21:43:40,355] DEBUG: checking whether disk sda has an empty extended [2009-10-09 21:43:40,356] DEBUG: extended is parted.Partition instance -- disk: fileSystem: None number: 4 path: /dev/sda4 type: 2 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x96aa7ac> ; logicals is [] [2009-10-09 21:43:40,356] DEBUG: removing empty extended partition from sda [2009-10-09 21:43:40,356] DEBUG: looking for device 'sda4'... [2009-10-09 21:43:40,356] DEBUG: found PartitionDevice instance (0x94b38ac) -- description = name = sda4 status = True parents = [] kids = 0 id = 4 uuid = None format = size = 129618.193359 major = 8 minor = 4 exists = True sysfs path = /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda4 label = None target size = 129618.193359 path = /dev/sda4 format args = [] grow = None max size = 0 bootable = None part type = 2 primary = None partedPartition = disk = [2009-10-09 21:43:40,375] DEBUG: removed sda4 (partition) from device tree [2009-10-09 21:43:40,378] DEBUG: registered action: Destroy Device sda4 (partition) [2009-10-09 21:43:40,380] DEBUG: getFormat('lvmpv') returning LVMPhysicalVolume instance [2009-10-09 21:43:40,389] DEBUG: added req0 (partition) to device tree [2009-10-09 21:43:40,389] DEBUG: registered action: Create Device req0 (partition) [2009-10-09 21:43:40,389] DEBUG: getFormat('None') returning DeviceFormat instance [2009-10-09 21:43:40,390] DEBUG: registered action: Create Format lvmpv on req0 (partition) [2009-10-09 21:43:40,392] DEBUG: getFormat('ext3') returning Ext3FS instance [2009-10-09 21:43:40,401] DEBUG: added req1 (partition) to device tree [2009-10-09 21:43:40,401] DEBUG: registered action: Create Device req1 (partition) [2009-10-09 21:43:40,401] DEBUG: getFormat('None') returning DeviceFormat instance [2009-10-09 21:43:40,401] DEBUG: registered action: Create Format ext3 on req1 (partition) [2009-10-09 21:43:40,402] WARNING: not sanity checking devices because I don't know how yet [2009-10-09 21:43:40,404] DEBUG: allocatePartitions: disks=[] ; partitions=[, ] [2009-10-09 21:43:40,404] DEBUG: removing all non-preexisting from disk(s) [2009-10-09 21:43:40,404] DEBUG: allocating partition: req1 ; disks: [] ; boot: True ; primary: False ; size: 200MB ; grow: False ; max_size: 0 [2009-10-09 21:43:40,405] DEBUG: checking freespace on sda [2009-10-09 21:43:40,405] DEBUG: getBestFreeSpaceRegion: disk=/dev/sda part_type=0 req_size=200MB boot=True best=None [2009-10-09 21:43:40,405] DEBUG: current free range is 63-312576704 (152625MB) [2009-10-09 21:43:40,406] DEBUG: updating use_disk to DiskDevice instance (0x92caecc) -- description = name = sda status = True parents = [] kids = 0 id = 0 uuid = None format = size = 152625.344238 major = 8 minor = 0 exists = True sysfs path = /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda label = None target size = 0 path = /dev/sda format args = [] removable = False partedDevice = partedDisk = (sda), type: 0 [2009-10-09 21:43:40,406] DEBUG: new free: parted.Geometry instance -- start: 63 end: 312576704 length: 312576642 device: PedGeometry: <_ped.Geometry object at 0x96b602c> (63-312576704 / 152625MB) [2009-10-09 21:43:40,407] DEBUG: found free space for bootable request [2009-10-09 21:43:40,408] DEBUG: created partition sda1 of 200MB and added it to parted.Disk instance -- type: msdos primaryPartitionCount: 1 lastPartitionNumber: 1 maxPrimaryPartitionCount: 4 partitions: [] device: PedDisk: <_ped.Disk object at 0x946476c> [2009-10-09 21:43:40,410] DEBUG: device req1 new partedPartition parted.Partition instance -- disk: fileSystem: None number: 1 path: /dev/sda1 type: 0 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x96aa7dc> has path /dev/sda1 [2009-10-09 21:43:40,415] DEBUG: device sda1 new partedPartition parted.Partition instance -- disk: fileSystem: None number: 1 path: /dev/sda1 type: 0 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x96aa71c> has path /dev/sda1 [2009-10-09 21:43:40,415] DEBUG: allocating partition: req0 ; disks: [] ; boot: False ; primary: False ; size: 1MB ; grow: True ; max_size: 0 [2009-10-09 21:43:40,415] DEBUG: checking freespace on sda [2009-10-09 21:43:40,415] DEBUG: getBestFreeSpaceRegion: disk=/dev/sda part_type=0 req_size=1MB boot=False best=None [2009-10-09 21:43:40,415] DEBUG: current free range is 409663-312576704 (152425MB) [2009-10-09 21:43:40,416] DEBUG: updating use_disk to DiskDevice instance (0x92caecc) -- description = name = sda status = True parents = [] kids = 1 id = 0 uuid = None format = size = 152625.344238 major = 8 minor = 0 exists = True sysfs path = /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda label = None target size = 0 path = /dev/sda format args = [] removable = False partedDevice = partedDisk = (sda), type: 0 [2009-10-09 21:43:40,416] DEBUG: new free: parted.Geometry instance -- start: 409663 end: 312576704 length: 312167042 device: PedGeometry: <_ped.Geometry object at 0x96b604c> (409663-312576704 / 152425MB) [2009-10-09 21:43:40,417] DEBUG: created partition sda2 of 1MB and added it to parted.Disk instance -- type: msdos primaryPartitionCount: 2 lastPartitionNumber: 2 maxPrimaryPartitionCount: 4 partitions: [, ] device: PedDisk: <_ped.Disk object at 0x946476c> [2009-10-09 21:43:40,418] DEBUG: device req0 new partedPartition parted.Partition instance -- disk: fileSystem: None number: 2 path: /dev/sda2 type: 0 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x96aa86c> has path /dev/sda2 [2009-10-09 21:43:40,422] DEBUG: device sda2 new partedPartition parted.Partition instance -- disk: fileSystem: None number: 2 path: /dev/sda2 type: 0 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x96aa7dc> has path /dev/sda2 [2009-10-09 21:43:40,423] DEBUG: growPartitions: disks=['sda'], partitions=['sda2', 'sda1'] [2009-10-09 21:43:40,423] DEBUG: growable requests are ['sda2'] [2009-10-09 21:43:40,423] DEBUG: growing requests on sda [2009-10-09 21:43:40,423] DEBUG: sda: sda1 (200MB) [2009-10-09 21:43:40,423] DEBUG: sda: sda2 (1MB) [2009-10-09 21:43:40,423] DEBUG: total free: 312164994 sectors ; largest: 312164994 sectors (152424MB) [2009-10-09 21:43:40,424] DEBUG: add sda2 (1MB/2048 sectors) to growable total [2009-10-09 21:43:40,424] DEBUG: growable total is now 2048 sectors [2009-10-09 21:43:40,424] DEBUG: sda2: base_size=1MB, max_size=0MB [2009-10-09 21:43:40,424] DEBUG: sda2: current_size=1MB (2048 sectors) [2009-10-09 21:43:40,424] DEBUG: sda2: 152425MB (312167042 sectors, or 100% of 312164994) [2009-10-09 21:43:40,424] DEBUG: checking constraints on max size... [2009-10-09 21:43:40,425] DEBUG: attempting to allocate maximum size: 152425MB [2009-10-09 21:43:40,425] DEBUG: allocatePartitions: disks=[] ; partitions=[, ] [2009-10-09 21:43:40,425] DEBUG: removing all non-preexisting from disk(s) [2009-10-09 21:43:40,426] DEBUG: device sda1 new partedPartition None has path None [2009-10-09 21:43:40,431] DEBUG: device sda2 new partedPartition None has path None [2009-10-09 21:43:40,433] DEBUG: allocating partition: req1 ; disks: [] ; boot: True ; primary: False ; size: 200MB ; grow: False ; max_size: 0 [2009-10-09 21:43:40,434] DEBUG: checking freespace on sda [2009-10-09 21:43:40,434] DEBUG: getBestFreeSpaceRegion: disk=/dev/sda part_type=0 req_size=200MB boot=True best=None [2009-10-09 21:43:40,434] DEBUG: current free range is 63-312576704 (152625MB) [2009-10-09 21:43:40,434] DEBUG: updating use_disk to DiskDevice instance (0x92caecc) -- description = name = sda status = True parents = [] kids = 0 id = 0 uuid = None format = size = 152625.344238 major = 8 minor = 0 exists = True sysfs path = /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda label = None target size = 0 path = /dev/sda format args = [] removable = False partedDevice = partedDisk = (sda), type: 0 [2009-10-09 21:43:40,435] DEBUG: new free: parted.Geometry instance -- start: 63 end: 312576704 length: 312576642 device: PedGeometry: <_ped.Geometry object at 0x96b648c> (63-312576704 / 152625MB) [2009-10-09 21:43:40,435] DEBUG: found free space for bootable request [2009-10-09 21:43:40,435] DEBUG: created partition sda1 of 200MB and added it to parted.Disk instance -- type: msdos primaryPartitionCount: 1 lastPartitionNumber: 1 maxPrimaryPartitionCount: 4 partitions: [] device: PedDisk: <_ped.Disk object at 0x946476c> [2009-10-09 21:43:40,437] DEBUG: device req1 new partedPartition parted.Partition instance -- disk: fileSystem: None number: 1 path: /dev/sda1 type: 0 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x96aa7ac> has path /dev/sda1 [2009-10-09 21:43:40,441] DEBUG: device sda1 new partedPartition parted.Partition instance -- disk: fileSystem: None number: 1 path: /dev/sda1 type: 0 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x96aa80c> has path /dev/sda1 [2009-10-09 21:43:40,441] DEBUG: allocating partition: req0 ; disks: [] ; boot: False ; primary: False ; size: 152425MB ; grow: True ; max_size: 0 [2009-10-09 21:43:40,442] DEBUG: checking freespace on sda [2009-10-09 21:43:40,442] DEBUG: getBestFreeSpaceRegion: disk=/dev/sda part_type=0 req_size=152425MB boot=False best=None [2009-10-09 21:43:40,442] DEBUG: current free range is 409663-312576704 (152425MB) [2009-10-09 21:43:40,442] DEBUG: updating use_disk to DiskDevice instance (0x92caecc) -- description = name = sda status = True parents = [] kids = 1 id = 0 uuid = None format = size = 152625.344238 major = 8 minor = 0 exists = True sysfs path = /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda label = None target size = 0 path = /dev/sda format args = [] removable = False partedDevice = partedDisk = (sda), type: 0 [2009-10-09 21:43:40,443] DEBUG: new free: parted.Geometry instance -- start: 409663 end: 312576704 length: 312167042 device: PedGeometry: <_ped.Geometry object at 0x96b652c> (409663-312576704 / 152425MB) [2009-10-09 21:43:40,443] DEBUG: created partition sda2 of 152425MB and added it to parted.Disk instance -- type: msdos primaryPartitionCount: 2 lastPartitionNumber: 2 maxPrimaryPartitionCount: 4 partitions: [, ] device: PedDisk: <_ped.Disk object at 0x946476c> [2009-10-09 21:43:40,445] DEBUG: device req0 new partedPartition parted.Partition instance -- disk: fileSystem: None number: 2 path: /dev/sda2 type: 0 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x96aa89c> has path /dev/sda2 [2009-10-09 21:43:40,449] DEBUG: device sda2 new partedPartition parted.Partition instance -- disk: fileSystem: None number: 2 path: /dev/sda2 type: 0 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x96aa7ac> has path /dev/sda2 [2009-10-09 21:43:40,452] DEBUG: getFormat('None') returning DeviceFormat instance [2009-10-09 21:43:40,453] DEBUG: added vg_parshwahost (lvmvg) to device tree [2009-10-09 21:43:40,453] DEBUG: registered action: Create Device vg_parshwahost (lvmvg) [2009-10-09 21:43:40,455] DEBUG: getFormat('ext4') returning Ext4FS instance [2009-10-09 21:43:40,458] DEBUG: added vg_parshwahost-lv_root (lvmlv) to device tree [2009-10-09 21:43:40,458] DEBUG: registered action: Create Device vg_parshwahost-lv_root (lvmlv) [2009-10-09 21:43:40,458] DEBUG: getFormat('None') returning DeviceFormat instance [2009-10-09 21:43:40,459] DEBUG: registered action: Create Format ext4 on vg_parshwahost-lv_root (lvmlv) [2009-10-09 21:43:40,460] DEBUG: getFormat('swap') returning SwapSpace instance [2009-10-09 21:43:40,463] DEBUG: added vg_parshwahost-lv_swap (lvmlv) to device tree [2009-10-09 21:43:40,463] DEBUG: registered action: Create Device vg_parshwahost-lv_swap (lvmlv) [2009-10-09 21:43:40,463] DEBUG: getFormat('None') returning DeviceFormat instance [2009-10-09 21:43:40,463] DEBUG: registered action: Create Format swap on vg_parshwahost-lv_swap (lvmlv) [2009-10-09 21:43:40,464] DEBUG: vg_parshwahost size is 152424MB [2009-10-09 21:43:40,464] DEBUG: lv vg_parshwahost-lv_root (LVMLogicalVolumeDevice instance (0x96b662c) -- description = name = vg_parshwahost-lv_root status = False parents = [] kids = 0 id = 17 uuid = None format = size = 1024 major = 0 minor = 0 exists = None sysfs path = label = None target size = 1024 path = /dev/mapper/vg_parshwahost-lv_root format args = [] target = None dmUuid = None VG device = percent = 0) uses 1024MB [2009-10-09 21:43:40,464] DEBUG: lv vg_parshwahost-lv_swap (LVMLogicalVolumeDevice instance (0x96b676c) -- description = name = vg_parshwahost-lv_swap status = False parents = [] kids = 0 id = 18 uuid = None format = size = 1008 major = 0 minor = 0 exists = None sysfs path = label = None target size = 1008 path = /dev/mapper/vg_parshwahost-lv_swap format args = [] target = None dmUuid = None VG device = percent = 0) uses 1008MB [2009-10-09 21:43:40,464] DEBUG: vg vg_parshwahost has 150392MB free [2009-10-09 21:43:40,465] DEBUG: vg_parshwahost size is 152424MB [2009-10-09 21:43:40,465] DEBUG: lv vg_parshwahost-lv_root (LVMLogicalVolumeDevice instance (0x96b662c) -- description = name = vg_parshwahost-lv_root status = False parents = [] kids = 0 id = 17 uuid = None format = size = 1024 major = 0 minor = 0 exists = None sysfs path = label = None target size = 1024 path = /dev/mapper/vg_parshwahost-lv_root format args = [] target = None dmUuid = None VG device = percent = 0) uses 1024MB [2009-10-09 21:43:40,465] DEBUG: lv vg_parshwahost-lv_swap (LVMLogicalVolumeDevice instance (0x96b676c) -- description = name = vg_parshwahost-lv_swap status = False parents = [] kids = 0 id = 18 uuid = None format = size = 1008 major = 0 minor = 0 exists = None sysfs path = label = None target size = 1008 path = /dev/mapper/vg_parshwahost-lv_swap format args = [] target = None dmUuid = None VG device = percent = 0) uses 1008MB [2009-10-09 21:43:40,465] DEBUG: vg vg_parshwahost has 150392MB free [2009-10-09 21:43:40,465] DEBUG: vg vg_parshwahost: 150392MB free ; lvs: ['lv_root', 'lv_swap'] [2009-10-09 21:43:40,466] DEBUG: used: 2032MB ; vg.size: 152424MB [2009-10-09 21:43:40,466] DEBUG: checking lv vg_parshwahost-lv_root: req_grow: True ; req_percent: 0 [2009-10-09 21:43:40,466] DEBUG: grow is 75788MB [2009-10-09 21:43:40,466] DEBUG: vg_parshwahost-lv_root getting 0MB (50%) of 0MB leftover space [2009-10-09 21:43:40,466] DEBUG: grow is now 75788MB [2009-10-09 21:43:40,466] DEBUG: max size is 76812MB [2009-10-09 21:43:40,467] DEBUG: lv vg_parshwahost-lv_root gets 75788MB [2009-10-09 21:43:40,467] DEBUG: checking lv vg_parshwahost-lv_swap: req_grow: True ; req_percent: 0 [2009-10-09 21:43:40,467] DEBUG: grow is 74603MB [2009-10-09 21:43:40,467] DEBUG: vg_parshwahost-lv_swap getting 0MB (100%) of 0MB leftover space [2009-10-09 21:43:40,467] DEBUG: grow is now 74603MB [2009-10-09 21:43:40,467] DEBUG: max size is 2016MB [2009-10-09 21:43:40,467] DEBUG: lv vg_parshwahost-lv_swap gets 1008MB [2009-10-09 21:43:40,468] DEBUG: trying to set lv vg_parshwahost-lv_root size to 76812MB [2009-10-09 21:43:40,468] DEBUG: vg_parshwahost size is 152424MB [2009-10-09 21:43:40,468] DEBUG: lv vg_parshwahost-lv_root (LVMLogicalVolumeDevice instance (0x96b662c) -- description = name = vg_parshwahost-lv_root status = False parents = [] kids = 0 id = 17 uuid = None format = size = 1024 major = 0 minor = 0 exists = None sysfs path = label = None target size = 1024 path = /dev/mapper/vg_parshwahost-lv_root format args = [] target = None dmUuid = None VG device = percent = 0) uses 1024MB [2009-10-09 21:43:40,468] DEBUG: lv vg_parshwahost-lv_swap (LVMLogicalVolumeDevice instance (0x96b676c) -- description = name = vg_parshwahost-lv_swap status = False parents = [] kids = 0 id = 18 uuid = None format = size = 1008 major = 0 minor = 0 exists = None sysfs path = label = None target size = 1008 path = /dev/mapper/vg_parshwahost-lv_swap format args = [] target = None dmUuid = None VG device = percent = 0) uses 1008MB [2009-10-09 21:43:40,469] DEBUG: vg vg_parshwahost has 150392MB free [2009-10-09 21:43:40,469] DEBUG: trying to set lv vg_parshwahost-lv_swap size to 2016MB [2009-10-09 21:43:40,469] DEBUG: vg_parshwahost size is 152424MB [2009-10-09 21:43:40,469] DEBUG: lv vg_parshwahost-lv_root (LVMLogicalVolumeDevice instance (0x96b662c) -- description = name = vg_parshwahost-lv_root status = False parents = [] kids = 0 id = 17 uuid = None format = size = 76812 major = 0 minor = 0 exists = None sysfs path = label = None target size = 76812 path = /dev/mapper/vg_parshwahost-lv_root format args = [] target = None dmUuid = None VG device = percent = 0) uses 76812MB [2009-10-09 21:43:40,469] DEBUG: lv vg_parshwahost-lv_swap (LVMLogicalVolumeDevice instance (0x96b676c) -- description = name = vg_parshwahost-lv_swap status = False parents = [] kids = 0 id = 18 uuid = None format = size = 1008 major = 0 minor = 0 exists = None sysfs path = label = None target size = 1008 path = /dev/mapper/vg_parshwahost-lv_swap format args = [] target = None dmUuid = None VG device = percent = 0) uses 1008MB [2009-10-09 21:43:40,470] DEBUG: vg vg_parshwahost has 74604MB free [2009-10-09 21:43:40,470] DEBUG: vg_parshwahost size is 152424MB [2009-10-09 21:43:40,470] DEBUG: lv vg_parshwahost-lv_root (LVMLogicalVolumeDevice instance (0x96b662c) -- description = name = vg_parshwahost-lv_root status = False parents = [] kids = 0 id = 17 uuid = None format = size = 76812 major = 0 minor = 0 exists = None sysfs path = label = None target size = 76812 path = /dev/mapper/vg_parshwahost-lv_root format args = [] target = None dmUuid = None VG device = percent = 0) uses 76812MB [2009-10-09 21:43:40,470] DEBUG: lv vg_parshwahost-lv_swap (LVMLogicalVolumeDevice instance (0x96b676c) -- description = name = vg_parshwahost-lv_swap status = False parents = [] kids = 0 id = 18 uuid = None format = size = 2016 major = 0 minor = 0 exists = None sysfs path = label = None target size = 2016 path = /dev/mapper/vg_parshwahost-lv_swap format args = [] target = None dmUuid = None VG device = percent = 0) uses 2016MB [2009-10-09 21:43:40,470] DEBUG: vg vg_parshwahost has 73596MB free [2009-10-09 21:43:40,471] DEBUG: vg vg_parshwahost has 73596MB free [2009-10-09 21:43:40,471] DEBUG: vg_parshwahost size is 152424MB [2009-10-09 21:43:40,471] DEBUG: lv vg_parshwahost-lv_root (LVMLogicalVolumeDevice instance (0x96b662c) -- description = name = vg_parshwahost-lv_root status = False parents = [] kids = 0 id = 17 uuid = None format = size = 76812 major = 0 minor = 0 exists = None sysfs path = label = None target size = 76812 path = /dev/mapper/vg_parshwahost-lv_root format args = [] target = None dmUuid = None VG device = percent = 0) uses 76812MB [2009-10-09 21:43:40,471] DEBUG: lv vg_parshwahost-lv_swap (LVMLogicalVolumeDevice instance (0x96b676c) -- description = name = vg_parshwahost-lv_swap status = False parents = [] kids = 0 id = 18 uuid = None format = size = 2016 major = 0 minor = 0 exists = None sysfs path = label = None target size = 2016 path = /dev/mapper/vg_parshwahost-lv_swap format args = [] target = None dmUuid = None VG device = percent = 0) uses 2016MB [2009-10-09 21:43:40,472] DEBUG: vg vg_parshwahost has 73596MB free [2009-10-09 21:43:40,472] DEBUG: giving leftover 73596MB to vg_parshwahost-lv_root [2009-10-09 21:43:40,472] DEBUG: trying to set lv vg_parshwahost-lv_root size to 150408MB [2009-10-09 21:43:40,472] DEBUG: vg_parshwahost size is 152424MB [2009-10-09 21:43:40,472] DEBUG: lv vg_parshwahost-lv_root (LVMLogicalVolumeDevice instance (0x96b662c) -- description = name = vg_parshwahost-lv_root status = False parents = [] kids = 0 id = 17 uuid = None format = size = 76812 major = 0 minor = 0 exists = None sysfs path = label = None target size = 76812 path = /dev/mapper/vg_parshwahost-lv_root format args = [] target = None dmUuid = None VG device = percent = 0) uses 76812MB [2009-10-09 21:43:40,472] DEBUG: lv vg_parshwahost-lv_swap (LVMLogicalVolumeDevice instance (0x96b676c) -- description = name = vg_parshwahost-lv_swap status = False parents = [] kids = 0 id = 18 uuid = None format = size = 2016 major = 0 minor = 0 exists = None sysfs path = label = None target size = 2016 path = /dev/mapper/vg_parshwahost-lv_swap format args = [] target = None dmUuid = None VG device = percent = 0) uses 2016MB [2009-10-09 21:43:40,473] DEBUG: vg vg_parshwahost has 73596MB free [2009-10-09 21:43:40,473] WARNING: not sanity checking storage config because I don't know how yet [2009-10-09 21:43:40,494] DEBUG: looking for device 'sda1'... [2009-10-09 21:43:40,494] DEBUG: found PartitionDevice instance (0x96b620c) -- description = name = sda1 status = False parents = [] kids = 0 id = 15 uuid = None format = size = 200.0 major = 0 minor = 0 exists = None sysfs path = label = None target size = 200 path = /dev/sda1 format args = [] grow = False max size = 0 bootable = True part type = 0 primary = False partedPartition = disk = [2009-10-09 21:43:40,497] DEBUG: looking for device 'sda2'... [2009-10-09 21:43:40,498] DEBUG: found PartitionDevice instance (0x96af2cc) -- description = name = sda2 status = False parents = [] kids = 1 id = 14 uuid = None format = size = 152425.313477 major = 0 minor = 0 exists = None sysfs path = label = None target size = 1 path = /dev/sda2 format args = [] grow = True max size = 0 bootable = False part type = 0 primary = False partedPartition = disk = [2009-10-09 21:43:47,746] DEBUG: action: Destroy Format None on VolGroup-lv_root (lvmlv) [2009-10-09 21:43:47,746] DEBUG: action: Destroy Device VolGroup-lv_root (lvmlv) [2009-10-09 21:43:47,747] DEBUG: action: Destroy Device VolGroup (lvmvg) [2009-10-09 21:43:47,747] DEBUG: action: Destroy Format None on sda1 (partition) [2009-10-09 21:43:47,747] DEBUG: action: Destroy Device sda1 (partition) [2009-10-09 21:43:47,747] DEBUG: action: Destroy Format None on sda10 (partition) [2009-10-09 21:43:47,748] DEBUG: action: Destroy Device sda10 (partition) [2009-10-09 21:43:47,748] DEBUG: action: Destroy Format None on sda10 (partition) [2009-10-09 21:43:47,748] DEBUG: action: Destroy Device sda10 (partition) [2009-10-09 21:43:47,749] DEBUG: action: Destroy Device sda2 (partition) [2009-10-09 21:43:47,749] DEBUG: action: Destroy Format None on sda3 (partition) [2009-10-09 21:43:47,749] DEBUG: action: Destroy Device sda3 (partition) [2009-10-09 21:43:47,750] DEBUG: action: Destroy Format None on sda5 (partition) [2009-10-09 21:43:47,750] DEBUG: action: Destroy Device sda5 (partition) [2009-10-09 21:43:47,750] DEBUG: action: Destroy Format None on sda5 (partition) [2009-10-09 21:43:47,750] DEBUG: action: Destroy Device sda5 (partition) [2009-10-09 21:43:47,751] DEBUG: action: Destroy Format None on sda5 (partition) [2009-10-09 21:43:47,751] DEBUG: action: Destroy Device sda5 (partition) [2009-10-09 21:43:47,751] DEBUG: action: Destroy Format None on sda5 (partition) [2009-10-09 21:43:47,751] DEBUG: action: Destroy Device sda5 (partition) [2009-10-09 21:43:47,752] DEBUG: action: Destroy Device sda5 (partition) [2009-10-09 21:43:47,752] DEBUG: action: Destroy Device sda4 (partition) [2009-10-09 21:43:47,752] DEBUG: action: Create Device sda2 (partition) [2009-10-09 21:43:47,752] DEBUG: action: Create Format lvmpv on sda2 (partition) [2009-10-09 21:43:47,753] DEBUG: action: Create Device sda1 (partition) [2009-10-09 21:43:47,753] DEBUG: action: Create Format ext3 on sda1 (partition) [2009-10-09 21:43:47,753] DEBUG: action: Create Device vg_parshwahost (lvmvg) [2009-10-09 21:43:47,753] DEBUG: action: Create Device vg_parshwahost-lv_root (lvmlv) [2009-10-09 21:43:47,754] DEBUG: action: Create Format ext4 on vg_parshwahost-lv_root (lvmlv) [2009-10-09 21:43:47,754] DEBUG: action: Create Device vg_parshwahost-lv_swap (lvmlv) [2009-10-09 21:43:47,754] DEBUG: action: Create Format swap on vg_parshwahost-lv_swap (lvmlv) [2009-10-09 21:43:47,754] DEBUG: pruning action queue... [2009-10-09 21:43:47,755] DEBUG: action 'Destroy Device VolGroup-lv_root (lvmlv)' (152650540) [2009-10-09 21:43:47,755] DEBUG: action 'Destroy Device VolGroup (lvmvg)' (156286540) [2009-10-09 21:43:47,755] DEBUG: action 'Destroy Device sda1 (partition)' (155601164) [2009-10-09 21:43:47,756] DEBUG: action 'Destroy Device sda10 (partition)' (155926124) [2009-10-09 21:43:47,756] DEBUG: action 'Destroy Device sda10 (partition)' (155926444) [2009-10-09 21:43:47,756] DEBUG: action 'Destroy Device sda2 (partition)' (158004364) [2009-10-09 21:43:47,757] DEBUG: action 'Destroy Device sda3 (partition)' (155924588) [2009-10-09 21:43:47,757] DEBUG: action 'Destroy Device sda5 (partition)' (155601388) [2009-10-09 21:43:47,757] DEBUG: action 'Destroy Device sda5 (partition)' (155924876) [2009-10-09 21:43:47,758] DEBUG: action 'Destroy Device sda5 (partition)' (155925356) [2009-10-09 21:43:47,758] DEBUG: action 'Destroy Device sda5 (partition)' (155925644) [2009-10-09 21:43:47,758] DEBUG: action 'Destroy Device sda5 (partition)' (158007020) [2009-10-09 21:43:47,759] DEBUG: action 'Destroy Device sda4 (partition)' (158007052) [2009-10-09 21:43:47,759] DEBUG: action 'Create Device sda2 (partition)' (158006988) [2009-10-09 21:43:47,759] DEBUG: action 'Create Device sda1 (partition)' (158032204) [2009-10-09 21:43:47,759] DEBUG: action 'Create Device vg_parshwahost (lvmvg)' (158033580) [2009-10-09 21:43:47,760] DEBUG: action 'Create Device vg_parshwahost-lv_root (lvmlv)' (158033004) [2009-10-09 21:43:47,760] DEBUG: action 'Create Device vg_parshwahost-lv_swap (lvmlv)' (158031980) [2009-10-09 21:43:47,760] DEBUG: action 'Destroy Format None on VolGroup-lv_root (lvmlv)' (156285516) [2009-10-09 21:43:47,761] DEBUG: action 'Destroy Format None on sda1 (partition)' (156285740) [2009-10-09 21:43:47,761] DEBUG: action 'Destroy Format None on sda10 (partition)' (158003948) [2009-10-09 21:43:47,761] DEBUG: action 'Destroy Format None on sda10 (partition)' (152667564) [2009-10-09 21:43:47,761] DEBUG: action 'Destroy Format None on sda3 (partition)' (152652876) [2009-10-09 21:43:47,761] DEBUG: action 'Destroy Format None on sda5 (partition)' (152652268) [2009-10-09 21:43:47,762] DEBUG: action 'Destroy Format None on sda5 (partition)' (152651724) [2009-10-09 21:43:47,762] DEBUG: action 'Destroy Format None on sda5 (partition)' (152651116) [2009-10-09 21:43:47,762] DEBUG: action 'Destroy Format None on sda5 (partition)' (152650508) [2009-10-09 21:43:47,762] DEBUG: action 'Create Format lvmpv on sda2 (partition)' (158007180) [2009-10-09 21:43:47,763] DEBUG: action 'Create Format ext3 on sda1 (partition)' (158032332) [2009-10-09 21:43:47,763] DEBUG: action 'Create Format ext4 on vg_parshwahost-lv_root (lvmlv)' (158032780) [2009-10-09 21:43:47,763] DEBUG: action 'Create Format swap on vg_parshwahost-lv_swap (lvmlv)' (158032620) [2009-10-09 21:43:47,763] DEBUG: action: Destroy Format None on VolGroup-lv_root (lvmlv) [2009-10-09 21:43:47,763] DEBUG: action: Destroy Device VolGroup-lv_root (lvmlv) [2009-10-09 21:43:47,763] DEBUG: action: Destroy Device VolGroup (lvmvg) [2009-10-09 21:43:47,764] DEBUG: action: Destroy Format None on sda1 (partition) [2009-10-09 21:43:47,764] DEBUG: action: Destroy Device sda1 (partition) [2009-10-09 21:43:47,764] DEBUG: action: Destroy Format None on sda10 (partition) [2009-10-09 21:43:47,764] DEBUG: action: Destroy Device sda10 (partition) [2009-10-09 21:43:47,764] DEBUG: action: Destroy Format None on sda10 (partition) [2009-10-09 21:43:47,764] DEBUG: action: Destroy Device sda10 (partition) [2009-10-09 21:43:47,765] DEBUG: action: Destroy Device sda2 (partition) [2009-10-09 21:43:47,765] DEBUG: action: Destroy Format None on sda3 (partition) [2009-10-09 21:43:47,765] DEBUG: action: Destroy Device sda3 (partition) [2009-10-09 21:43:47,765] DEBUG: action: Destroy Format None on sda5 (partition) [2009-10-09 21:43:47,765] DEBUG: action: Destroy Device sda5 (partition) [2009-10-09 21:43:47,765] DEBUG: action: Destroy Format None on sda5 (partition) [2009-10-09 21:43:47,766] DEBUG: action: Destroy Device sda5 (partition) [2009-10-09 21:43:47,766] DEBUG: action: Destroy Format None on sda5 (partition) [2009-10-09 21:43:47,766] DEBUG: action: Destroy Device sda5 (partition) [2009-10-09 21:43:47,766] DEBUG: action: Destroy Format None on sda5 (partition) [2009-10-09 21:43:47,766] DEBUG: action: Destroy Device sda5 (partition) [2009-10-09 21:43:47,766] DEBUG: action: Destroy Device sda5 (partition) [2009-10-09 21:43:47,766] DEBUG: action: Destroy Device sda4 (partition) [2009-10-09 21:43:47,767] DEBUG: action: Create Device sda2 (partition) [2009-10-09 21:43:47,767] DEBUG: action: Create Format lvmpv on sda2 (partition) [2009-10-09 21:43:47,767] DEBUG: action: Create Device sda1 (partition) [2009-10-09 21:43:47,767] DEBUG: action: Create Format ext3 on sda1 (partition) [2009-10-09 21:43:47,767] DEBUG: action: Create Device vg_parshwahost (lvmvg) [2009-10-09 21:43:47,767] DEBUG: action: Create Device vg_parshwahost-lv_root (lvmlv) [2009-10-09 21:43:47,768] DEBUG: action: Create Format ext4 on vg_parshwahost-lv_root (lvmlv) [2009-10-09 21:43:47,768] DEBUG: action: Create Device vg_parshwahost-lv_swap (lvmlv) [2009-10-09 21:43:47,768] DEBUG: action: Create Format swap on vg_parshwahost-lv_swap (lvmlv) [2009-10-09 21:43:47,768] DEBUG: sorting actions... [2009-10-09 21:43:47,768] DEBUG: cmp: 1 -- Destroy Device VolGroup-lv_root (lvmlv) | Destroy Format None on VolGroup-lv_root (lvmlv) [2009-10-09 21:43:47,768] DEBUG: cmp: 1 -- Destroy Device VolGroup (lvmvg) | Destroy Device VolGroup-lv_root (lvmlv) [2009-10-09 21:43:47,769] DEBUG: cmp: 1 -- Destroy Format None on sda1 (partition) | Destroy Device VolGroup (lvmvg) [2009-10-09 21:43:47,769] DEBUG: cmp: 1 -- Destroy Device sda1 (partition) | Destroy Format None on sda1 (partition) [2009-10-09 21:43:47,769] DEBUG: cmp: -1 -- Destroy Format None on sda10 (partition) | Destroy Device sda1 (partition) [2009-10-09 21:43:47,769] DEBUG: cmp: 1 -- Destroy Format None on sda10 (partition) | Destroy Device VolGroup (lvmvg) [2009-10-09 21:43:47,769] DEBUG: cmp: -1 -- Destroy Format None on sda10 (partition) | Destroy Device sda1 (partition) [2009-10-09 21:43:47,770] DEBUG: cmp: -1 -- Destroy Format None on sda10 (partition) | Destroy Format None on sda1 (partition) [2009-10-09 21:43:47,770] DEBUG: cmp: 1 -- Destroy Device sda10 (partition) | Destroy Format None on sda10 (partition) [2009-10-09 21:43:47,770] DEBUG: cmp: -1 -- Destroy Device sda10 (partition) | Destroy Device sda1 (partition) [2009-10-09 21:43:47,770] DEBUG: cmp: -1 -- Destroy Device sda10 (partition) | Destroy Format None on sda1 (partition) [2009-10-09 21:43:47,770] DEBUG: cmp: 0 -- Destroy Format None on sda10 (partition) | Destroy Format None on sda10 (partition) [2009-10-09 21:43:47,771] DEBUG: cmp: -1 -- Destroy Format None on sda10 (partition) | Destroy Format None on sda1 (partition) [2009-10-09 21:43:47,771] DEBUG: cmp: -1 -- Destroy Format None on sda10 (partition) | Destroy Device sda10 (partition) [2009-10-09 21:43:47,771] DEBUG: cmp: 1 -- Destroy Device sda10 (partition) | Destroy Format None on sda10 (partition) [2009-10-09 21:43:47,771] DEBUG: cmp: -1 -- Destroy Device sda10 (partition) | Destroy Format None on sda1 (partition) [2009-10-09 21:43:47,771] DEBUG: cmp: 0 -- Destroy Device sda10 (partition) | Destroy Device sda10 (partition) [2009-10-09 21:43:47,772] DEBUG: cmp: 1 -- Destroy Device sda2 (partition) | Destroy Format None on sda10 (partition) [2009-10-09 21:43:47,772] DEBUG: cmp: -1 -- Destroy Device sda2 (partition) | Destroy Format None on sda1 (partition) [2009-10-09 21:43:47,772] DEBUG: cmp: 1 -- Destroy Device sda2 (partition) | Destroy Device sda10 (partition) [2009-10-09 21:43:47,773] DEBUG: cmp: 1 -- Destroy Format None on sda3 (partition) | Destroy Device sda10 (partition) [2009-10-09 21:43:47,773] DEBUG: cmp: -1 -- Destroy Format None on sda3 (partition) | Destroy Format None on sda1 (partition) [2009-10-09 21:43:47,773] DEBUG: cmp: -1 -- Destroy Format None on sda3 (partition) | Destroy Device sda2 (partition) [2009-10-09 21:43:47,773] DEBUG: cmp: 1 -- Destroy Format None on sda3 (partition) | Destroy Device sda10 (partition) [2009-10-09 21:43:47,773] DEBUG: cmp: 1 -- Destroy Device sda3 (partition) | Destroy Device sda10 (partition) [2009-10-09 21:43:47,774] DEBUG: cmp: -1 -- Destroy Device sda3 (partition) | Destroy Device sda2 (partition) [2009-10-09 21:43:47,774] DEBUG: cmp: 1 -- Destroy Device sda3 (partition) | Destroy Format None on sda3 (partition) [2009-10-09 21:43:47,774] DEBUG: cmp: 1 -- Destroy Format None on sda5 (partition) | Destroy Device sda10 (partition) [2009-10-09 21:43:47,774] DEBUG: cmp: -1 -- Destroy Format None on sda5 (partition) | Destroy Device sda2 (partition) [2009-10-09 21:43:47,774] DEBUG: cmp: -1 -- Destroy Format None on sda5 (partition) | Destroy Device sda3 (partition) [2009-10-09 21:43:47,775] DEBUG: cmp: -1 -- Destroy Format None on sda5 (partition) | Destroy Format None on sda3 (partition) [2009-10-09 21:43:47,775] DEBUG: cmp: 1 -- Destroy Device sda5 (partition) | Destroy Device sda10 (partition) [2009-10-09 21:43:47,775] DEBUG: cmp: -1 -- Destroy Device sda5 (partition) | Destroy Device sda2 (partition) [2009-10-09 21:43:47,775] DEBUG: cmp: -1 -- Destroy Device sda5 (partition) | Destroy Format None on sda3 (partition) [2009-10-09 21:43:47,775] DEBUG: cmp: 1 -- Destroy Device sda5 (partition) | Destroy Format None on sda5 (partition) [2009-10-09 21:43:47,775] DEBUG: cmp: 0 -- Destroy Format None on sda5 (partition) | Destroy Format None on sda5 (partition) [2009-10-09 21:43:47,776] DEBUG: cmp: -1 -- Destroy Format None on sda5 (partition) | Destroy Device sda2 (partition) [2009-10-09 21:43:47,776] DEBUG: cmp: -1 -- Destroy Format None on sda5 (partition) | Destroy Format None on sda3 (partition) [2009-10-09 21:43:47,776] DEBUG: cmp: -1 -- Destroy Format None on sda5 (partition) | Destroy Device sda5 (partition) [2009-10-09 21:43:47,776] DEBUG: cmp: 1 -- Destroy Device sda5 (partition) | Destroy Format None on sda5 (partition) [2009-10-09 21:43:47,776] DEBUG: cmp: -1 -- Destroy Device sda5 (partition) | Destroy Device sda3 (partition) [2009-10-09 21:43:47,777] DEBUG: cmp: 0 -- Destroy Device sda5 (partition) | Destroy Device sda5 (partition) [2009-10-09 21:43:47,777] DEBUG: cmp: -1 -- Destroy Device sda5 (partition) | Destroy Format None on sda3 (partition) [2009-10-09 21:43:47,777] DEBUG: cmp: 0 -- Destroy Format None on sda5 (partition) | Destroy Format None on sda5 (partition) [2009-10-09 21:43:47,777] DEBUG: cmp: -1 -- Destroy Format None on sda5 (partition) | Destroy Device sda3 (partition) [2009-10-09 21:43:47,777] DEBUG: cmp: -1 -- Destroy Format None on sda5 (partition) | Destroy Device sda5 (partition) [2009-10-09 21:43:47,778] DEBUG: cmp: -1 -- Destroy Format None on sda5 (partition) | Destroy Device sda5 (partition) [2009-10-09 21:43:47,778] DEBUG: cmp: 1 -- Destroy Device sda5 (partition) | Destroy Format None on sda5 (partition) [2009-10-09 21:43:47,778] DEBUG: cmp: -1 -- Destroy Device sda5 (partition) | Destroy Device sda3 (partition) [2009-10-09 21:43:47,778] DEBUG: cmp: 0 -- Destroy Device sda5 (partition) | Destroy Device sda5 (partition) [2009-10-09 21:43:47,778] DEBUG: cmp: -1 -- Destroy Device sda5 (partition) | Destroy Format None on sda3 (partition) [2009-10-09 21:43:47,779] DEBUG: cmp: 0 -- Destroy Format None on sda5 (partition) | Destroy Format None on sda5 (partition) [2009-10-09 21:43:47,779] DEBUG: cmp: -1 -- Destroy Format None on sda5 (partition) | Destroy Device sda3 (partition) [2009-10-09 21:43:47,779] DEBUG: cmp: -1 -- Destroy Format None on sda5 (partition) | Destroy Device sda5 (partition) [2009-10-09 21:43:47,779] DEBUG: cmp: -1 -- Destroy Format None on sda5 (partition) | Destroy Device sda5 (partition) [2009-10-09 21:43:47,779] DEBUG: cmp: -1 -- Destroy Format None on sda5 (partition) | Destroy Device sda5 (partition) [2009-10-09 21:43:47,779] DEBUG: cmp: 1 -- Destroy Device sda5 (partition) | Destroy Format None on sda5 (partition) [2009-10-09 21:43:47,780] DEBUG: cmp: -1 -- Destroy Device sda5 (partition) | Destroy Format None on sda3 (partition) [2009-10-09 21:43:47,780] DEBUG: cmp: 0 -- Destroy Device sda5 (partition) | Destroy Device sda5 (partition) [2009-10-09 21:43:47,780] DEBUG: cmp: 0 -- Destroy Device sda5 (partition) | Destroy Device sda5 (partition) [2009-10-09 21:43:47,780] DEBUG: cmp: 1 -- Destroy Device sda5 (partition) | Destroy Format None on sda5 (partition) [2009-10-09 21:43:47,780] DEBUG: cmp: -1 -- Destroy Device sda5 (partition) | Destroy Format None on sda3 (partition) [2009-10-09 21:43:47,781] DEBUG: cmp: 0 -- Destroy Device sda5 (partition) | Destroy Device sda5 (partition) [2009-10-09 21:43:47,781] DEBUG: cmp: 0 -- Destroy Device sda5 (partition) | Destroy Device sda5 (partition) [2009-10-09 21:43:47,781] DEBUG: cmp: 1 -- Destroy Device sda4 (partition) | Destroy Format None on sda5 (partition) [2009-10-09 21:43:47,781] DEBUG: cmp: -1 -- Destroy Device sda4 (partition) | Destroy Format None on sda3 (partition) [2009-10-09 21:43:47,781] DEBUG: cmp: 1 -- Destroy Device sda4 (partition) | Destroy Device sda5 (partition) [2009-10-09 21:43:47,782] DEBUG: cmp: 1 -- Destroy Device sda4 (partition) | Destroy Device sda5 (partition) [2009-10-09 21:43:47,782] DEBUG: cmp: 1 -- Create Device sda2 (partition) | Destroy Device sda5 (partition) [2009-10-09 21:43:47,782] DEBUG: cmp: 1 -- Create Device sda2 (partition) | Destroy Format None on sda3 (partition) [2009-10-09 21:43:47,782] DEBUG: cmp: 1 -- Create Device sda2 (partition) | Destroy Format None on sda1 (partition) [2009-10-09 21:43:47,782] DEBUG: cmp: 1 -- Create Device sda2 (partition) | Destroy Device sda1 (partition) [2009-10-09 21:43:47,783] DEBUG: cmp: 1 -- Create Format lvmpv on sda2 (partition) | Destroy Device sda5 (partition) [2009-10-09 21:43:47,783] DEBUG: cmp: 1 -- Create Format lvmpv on sda2 (partition) | Destroy Format None on sda3 (partition) [2009-10-09 21:43:47,783] DEBUG: cmp: 1 -- Create Format lvmpv on sda2 (partition) | Destroy Format None on sda1 (partition) [2009-10-09 21:43:47,783] DEBUG: cmp: 1 -- Create Format lvmpv on sda2 (partition) | Create Device sda2 (partition) [2009-10-09 21:43:47,783] DEBUG: cmp: 1 -- Create Device sda1 (partition) | Destroy Device sda5 (partition) [2009-10-09 21:43:47,784] DEBUG: cmp: 1 -- Create Device sda1 (partition) | Destroy Device sda3 (partition) [2009-10-09 21:43:47,784] DEBUG: cmp: 1 -- Create Device sda1 (partition) | Destroy Device sda1 (partition) [2009-10-09 21:43:47,784] DEBUG: cmp: -1 -- Create Device sda1 (partition) | Create Format lvmpv on sda2 (partition) [2009-10-09 21:43:47,784] DEBUG: cmp: -1 -- Create Device sda1 (partition) | Create Device sda2 (partition) [2009-10-09 21:43:47,784] DEBUG: cmp: 1 -- Create Format ext3 on sda1 (partition) | Destroy Device sda5 (partition) [2009-10-09 21:43:47,784] DEBUG: cmp: 1 -- Create Format ext3 on sda1 (partition) | Destroy Device sda2 (partition) [2009-10-09 21:43:47,785] DEBUG: cmp: 1 -- Create Format ext3 on sda1 (partition) | Create Device sda1 (partition) [2009-10-09 21:43:47,785] DEBUG: cmp: -1 -- Create Format ext3 on sda1 (partition) | Create Format lvmpv on sda2 (partition) [2009-10-09 21:43:47,785] DEBUG: cmp: -1 -- Create Format ext3 on sda1 (partition) | Create Device sda2 (partition) [2009-10-09 21:43:47,785] DEBUG: cmp: 1 -- Create Device vg_parshwahost (lvmvg) | Destroy Device sda5 (partition) [2009-10-09 21:43:47,785] DEBUG: cmp: 1 -- Create Device vg_parshwahost (lvmvg) | Destroy Format None on sda1 (partition) [2009-10-09 21:43:47,786] DEBUG: cmp: 1 -- Create Device vg_parshwahost (lvmvg) | Create Format ext3 on sda1 (partition) [2009-10-09 21:43:47,786] DEBUG: cmp: 1 -- Create Device vg_parshwahost (lvmvg) | Create Format lvmpv on sda2 (partition) [2009-10-09 21:43:47,786] DEBUG: cmp: 1 -- Create Device vg_parshwahost-lv_root (lvmlv) | Destroy Device sda5 (partition) [2009-10-09 21:43:47,786] DEBUG: cmp: 1 -- Create Device vg_parshwahost-lv_root (lvmlv) | Destroy Format None on sda1 (partition) [2009-10-09 21:43:47,786] DEBUG: cmp: 1 -- Create Device vg_parshwahost-lv_root (lvmlv) | Create Device sda2 (partition) [2009-10-09 21:43:47,786] DEBUG: cmp: 1 -- Create Device vg_parshwahost-lv_root (lvmlv) | Create Device vg_parshwahost (lvmvg) [2009-10-09 21:43:47,787] DEBUG: cmp: 1 -- Create Format ext4 on vg_parshwahost-lv_root (lvmlv) | Destroy Device sda5 (partition) [2009-10-09 21:43:47,787] DEBUG: cmp: 1 -- Create Format ext4 on vg_parshwahost-lv_root (lvmlv) | Destroy Device sda1 (partition) [2009-10-09 21:43:47,787] DEBUG: cmp: 1 -- Create Format ext4 on vg_parshwahost-lv_root (lvmlv) | Create Format lvmpv on sda2 (partition) [2009-10-09 21:43:47,787] DEBUG: cmp: 1 -- Create Format ext4 on vg_parshwahost-lv_root (lvmlv) | Create Device vg_parshwahost-lv_root (lvmlv) [2009-10-09 21:43:47,787] DEBUG: cmp: 1 -- Create Device vg_parshwahost-lv_swap (lvmlv) | Destroy Device sda5 (partition) [2009-10-09 21:43:47,788] DEBUG: cmp: 1 -- Create Device vg_parshwahost-lv_swap (lvmlv) | Create Device sda1 (partition) [2009-10-09 21:43:47,788] DEBUG: cmp: 1 -- Create Device vg_parshwahost-lv_swap (lvmlv) | Create Device vg_parshwahost (lvmvg) [2009-10-09 21:43:47,788] DEBUG: cmp: 0 -- Create Device vg_parshwahost-lv_swap (lvmlv) | Create Format ext4 on vg_parshwahost-lv_root (lvmlv) [2009-10-09 21:43:47,788] DEBUG: cmp: 1 -- Create Format swap on vg_parshwahost-lv_swap (lvmlv) | Destroy Device sda5 (partition) [2009-10-09 21:43:47,788] DEBUG: cmp: 1 -- Create Format swap on vg_parshwahost-lv_swap (lvmlv) | Create Format ext3 on sda1 (partition) [2009-10-09 21:43:47,789] DEBUG: cmp: 0 -- Create Format swap on vg_parshwahost-lv_swap (lvmlv) | Create Device vg_parshwahost-lv_root (lvmlv) [2009-10-09 21:43:47,789] DEBUG: cmp: 1 -- Create Format swap on vg_parshwahost-lv_swap (lvmlv) | Create Device vg_parshwahost-lv_swap (lvmlv) [2009-10-09 21:43:47,789] DEBUG: action: Destroy Format None on VolGroup-lv_root (lvmlv) [2009-10-09 21:43:47,789] DEBUG: action: Destroy Device VolGroup-lv_root (lvmlv) [2009-10-09 21:43:47,789] DEBUG: action: Destroy Device VolGroup (lvmvg) [2009-10-09 21:43:47,789] DEBUG: action: Destroy Format None on sda10 (partition) [2009-10-09 21:43:47,790] DEBUG: action: Destroy Format None on sda10 (partition) [2009-10-09 21:43:47,790] DEBUG: action: Destroy Device sda10 (partition) [2009-10-09 21:43:47,790] DEBUG: action: Destroy Device sda10 (partition) [2009-10-09 21:43:47,790] DEBUG: action: Destroy Format None on sda5 (partition) [2009-10-09 21:43:47,790] DEBUG: action: Destroy Format None on sda5 (partition) [2009-10-09 21:43:47,790] DEBUG: action: Destroy Format None on sda5 (partition) [2009-10-09 21:43:47,791] DEBUG: action: Destroy Format None on sda5 (partition) [2009-10-09 21:43:47,791] DEBUG: action: Destroy Device sda5 (partition) [2009-10-09 21:43:47,791] DEBUG: action: Destroy Device sda5 (partition) [2009-10-09 21:43:47,791] DEBUG: action: Destroy Device sda5 (partition) [2009-10-09 21:43:47,791] DEBUG: action: Destroy Device sda5 (partition) [2009-10-09 21:43:47,791] DEBUG: action: Destroy Device sda5 (partition) [2009-10-09 21:43:47,792] DEBUG: action: Destroy Device sda4 (partition) [2009-10-09 21:43:47,792] DEBUG: action: Destroy Format None on sda3 (partition) [2009-10-09 21:43:47,792] DEBUG: action: Destroy Device sda3 (partition) [2009-10-09 21:43:47,792] DEBUG: action: Destroy Device sda2 (partition) [2009-10-09 21:43:47,792] DEBUG: action: Destroy Format None on sda1 (partition) [2009-10-09 21:43:47,792] DEBUG: action: Destroy Device sda1 (partition) [2009-10-09 21:43:47,792] DEBUG: action: Create Device sda1 (partition) [2009-10-09 21:43:47,793] DEBUG: action: Create Format ext3 on sda1 (partition) [2009-10-09 21:43:47,793] DEBUG: action: Create Device sda2 (partition) [2009-10-09 21:43:47,793] DEBUG: action: Create Format lvmpv on sda2 (partition) [2009-10-09 21:43:47,793] DEBUG: action: Create Device vg_parshwahost (lvmvg) [2009-10-09 21:43:47,794] DEBUG: action: Create Device vg_parshwahost-lv_root (lvmlv) [2009-10-09 21:43:47,794] DEBUG: action: Create Format ext4 on vg_parshwahost-lv_root (lvmlv) [2009-10-09 21:43:47,794] DEBUG: action: Create Device vg_parshwahost-lv_swap (lvmlv) [2009-10-09 21:43:47,794] DEBUG: action: Create Format swap on vg_parshwahost-lv_swap (lvmlv) [2009-10-09 21:43:47,794] DEBUG: resetting parted disks... [2009-10-09 21:43:47,796] INFO: executing action: Destroy Format None on VolGroup-lv_root (lvmlv) [2009-10-09 21:43:48,296] DEBUG: zeroing out beginning and end of /dev/mapper/VolGroup-lv_root... [2009-10-09 21:43:54,192] INFO: executing action: Destroy Device VolGroup-lv_root (lvmlv) [2009-10-09 21:43:56,371] INFO: executing action: Destroy Device VolGroup (lvmvg) [2009-10-09 21:43:57,815] WARNING: failed to notify kernel of change: invalid sysfs path [2009-10-09 21:43:59,751] INFO: executing action: Destroy Format None on sda10 (partition) [2009-10-09 21:43:59,762] DEBUG: zeroing out beginning and end of /dev/sda10... [2009-10-09 21:44:00,154] INFO: executing action: Destroy Format None on sda10 (partition) [2009-10-09 21:44:05,902] INFO: executing action: Destroy Device sda10 (partition) [2009-10-09 21:44:08,397] INFO: executing action: Destroy Device sda10 (partition) [2009-10-09 21:44:10,682] INFO: executing action: Destroy Format None on sda5 (partition) [2009-10-09 21:44:12,512] DEBUG: zeroing out beginning and end of /dev/sda5... [2009-10-09 21:44:12,888] INFO: executing action: Destroy Format None on sda5 (partition) [2009-10-09 21:44:12,900] DEBUG: zeroing out beginning and end of /dev/sda6... [2009-10-09 21:44:13,279] INFO: executing action: Destroy Format None on sda5 (partition) [2009-10-09 21:44:13,285] DEBUG: zeroing out beginning and end of /dev/sda7... [2009-10-09 21:44:13,662] INFO: executing action: Destroy Format None on sda5 (partition) [2009-10-09 21:44:13,674] DEBUG: zeroing out beginning and end of /dev/sda8... [2009-10-09 21:44:14,053] INFO: executing action: Destroy Device sda5 (partition) [2009-10-09 21:44:15,945] INFO: executing action: Destroy Device sda5 (partition) [2009-10-09 21:44:17,644] INFO: executing action: Destroy Device sda5 (partition) [2009-10-09 21:44:19,339] INFO: executing action: Destroy Device sda5 (partition) [2009-10-09 21:44:21,147] INFO: executing action: Destroy Device sda5 (partition) [2009-10-09 21:44:23,003] INFO: executing action: Destroy Device sda4 (partition) [2009-10-09 21:44:24,330] INFO: executing action: Destroy Format None on sda3 (partition) [2009-10-09 21:44:28,563] INFO: executing action: Destroy Device sda3 (partition) [2009-10-09 21:44:29,964] INFO: executing action: Destroy Device sda2 (partition) [2009-10-09 21:44:31,120] INFO: executing action: Destroy Format None on sda1 (partition) [2009-10-09 21:44:31,131] DEBUG: zeroing out beginning and end of /dev/sda1... [2009-10-09 21:44:31,386] INFO: executing action: Destroy Device sda1 (partition) [2009-10-09 21:44:32,640] INFO: executing action: Create Device sda1 (partition) [2009-10-09 21:44:32,644] INFO: NOTE: recursive device creation disabled [2009-10-09 21:44:33,772] DEBUG: zeroing out beginning and end of /dev/sda1... [2009-10-09 21:44:33,921] DEBUG: device sda1 new partedPartition parted.Partition instance -- disk: fileSystem: None number: 1 path: /dev/sda1 type: 0 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x96cdbcc> has path /dev/sda1 [2009-10-09 21:44:34,005] INFO: executing action: Create Format ext3 on sda1 (partition) [2009-10-09 21:44:41,828] ERROR: failed to run tune2fs on /dev/sda1: /usr/sbin/tune2fs can not be run [2009-10-09 21:44:41,966] DEBUG: sda1 sysfsPath set to /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda1 [2009-10-09 21:44:41,993] INFO: executing action: Create Device sda2 (partition) [2009-10-09 21:44:41,994] INFO: NOTE: recursive device creation disabled [2009-10-09 21:44:41,997] DEBUG: disk sda: partition sda1 has geom parted.Geometry instance -- start: 63 end: 409662 length: 409600 device: PedGeometry: <_ped.Geometry object at 0x96fd1ec> [2009-10-09 21:44:42,578] DEBUG: zeroing out beginning and end of /dev/sda2... [2009-10-09 21:44:42,673] DEBUG: device sda2 new partedPartition parted.Partition instance -- disk: fileSystem: None number: 2 path: /dev/sda2 type: 0 name: None active: True busy: False geometry: PedPartition: <_ped.Partition object at 0x96cdc8c> has path /dev/sda2 [2009-10-09 21:44:42,760] INFO: executing action: Create Format lvmpv on sda2 (partition) [2009-10-09 21:44:43,419] DEBUG: zeroing out beginning and end of /dev/sda2... [2009-10-09 21:44:43,736] DEBUG: sda2 sysfsPath set to /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda2 [2009-10-09 21:44:43,766] INFO: executing action: Create Device vg_parshwahost (lvmvg) [2009-10-09 21:44:43,769] INFO: NOTE: recursive device creation disabled [2009-10-09 21:44:44,232] INFO: executing action: Create Device vg_parshwahost-lv_root (lvmlv) [2009-10-09 21:44:44,235] INFO: NOTE: recursive device creation disabled ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Thanks, Parshwa -------------- next part -------------- An HTML attachment was scrubbed... URL: From boni.vivek at gmail.com Mon Oct 12 06:07:39 2009 From: boni.vivek at gmail.com (Vivek Shah) Date: Mon, 12 Oct 2009 11:37:39 +0530 Subject: [fedora-india] Request for media Message-ID: Hi, My present system is hopelessly broken with a hard disk crash. Can someone provide me with an Fedora rawhide snapshot install CD/DVD ? If that is not possible, a Fedora 11 install DVD would be ideal or a CD. I will be travelling to Kolkata day after tomorrow and will be there for 10 days with a very flickery USB modem so the requirement for the CD/DVD is urgent. Thanks and Regards, Vivek From debarshi.ray at gmail.com Mon Oct 12 13:31:53 2009 From: debarshi.ray at gmail.com (Debarshi Ray) Date: Mon, 12 Oct 2009 16:31:53 +0300 Subject: [fedora-india] I want to ask something In-Reply-To: <7856eaf20910090422m645eb85dna0383013013f8f6f@mail.gmail.com> References: <7856eaf20910090422m645eb85dna0383013013f8f6f@mail.gmail.com> Message-ID: <3170f42f0910120631p10af7749w9e0f1141871e0135@mail.gmail.com> > Here is the error message which is > coming whcih I? am not able to understand, please explain me. Here is this: > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > anaconda 11.5.0.59-1.fc11 exception report > Traceback (most recent call first): > ? File "/usr/lib/anaconda/storage/devicelibs/lvm.py", line 357, in lvcreate > ??? raise LVMError("lvcreate failed for %s/%s" % (vg_name, lv_name)) > ? File "/usr/lib/anaconda/storage/devices.py", line 2137, in create > ??? lvm.lvcreate(self.vg.name, self._name, self.size) > ? File "/usr/lib/anaconda/storage/deviceaction.py", line 203, in execute > ??? self.device.create(intf=intf) > ? File "/usr/lib/anaconda/storage/devicetree.py", line 671, in > processActions > ??? action.execute(intf=self.intf) > ? File "/usr/lib/anaconda/storage/__init__.py", line 238, in doIt > ??? self.devicetree.processActions() > ? File "/usr/lib/anaconda/packages.py", line 117, in turnOnFilesystems > ??? anaconda.id.storage.doIt() > LVMError: lvcreate failed for vg_parshwahost/lv_root Looks like you hit one of those Anaconda storage layer bugs, due to the rewrite in Fedora 11, and got it to crash. You can check http://bugzilla.redhat.com/ if it has already been reported or not. If not you can file it. You have not mentioned some important information like what partitioning layout did you chose. Just saying that you installed Windows in 60GB out of 160GB is not enough. Was it the first partition on the disk? Did you choose any custom partitioning scheme for Fedora? What filesystems? And so on. You can also take a look at http://fedoraproject.org/wiki/Anaconda/BugReporting Cheers, Debarshi -- One reason that life is complex is that it has a real part and an imaginary part. -- Andrew Koenig From debarshi.ray at gmail.com Mon Oct 12 13:51:47 2009 From: debarshi.ray at gmail.com (Debarshi Ray) Date: Mon, 12 Oct 2009 16:51:47 +0300 Subject: [fedora-india] I want to ask something In-Reply-To: <3170f42f0910120631p10af7749w9e0f1141871e0135@mail.gmail.com> References: <7856eaf20910090422m645eb85dna0383013013f8f6f@mail.gmail.com> <3170f42f0910120631p10af7749w9e0f1141871e0135@mail.gmail.com> Message-ID: <3170f42f0910120651v60c9dd31te68dcf3b0d90b2c7@mail.gmail.com> Looks like this is: https://bugzilla.redhat.com/496760 Cheers, Debarshi -- One reason that life is complex is that it has a real part and an imaginary part. -- Andrew Koenig From writetolali at gmail.com Mon Oct 12 13:54:44 2009 From: writetolali at gmail.com (pushpinder singh) Date: Mon, 12 Oct 2009 19:24:44 +0530 Subject: [fedora-india] Need interface for Garmin GPS devices for fedora In-Reply-To: References: Message-ID: <4AD33524.2000302@gmail.com> Ola fellows, does anyone know of the interface softwares available for Garmin GPS (Global Positioning Satellite Systems) devices with fedora For USB connections to import and use the GPS data in your system. has anyone used them? please pass on information. cheers Pushpinder From yogsin at gmail.com Mon Oct 12 16:31:45 2009 From: yogsin at gmail.com (yogendra singh) Date: Mon, 12 Oct 2009 22:01:45 +0530 Subject: [fedora-india] I want to ask something In-Reply-To: <7856eaf20910090422m645eb85dna0383013013f8f6f@mail.gmail.com> References: <7856eaf20910090422m645eb85dna0383013013f8f6f@mail.gmail.com> Message-ID: <74854c580910120931q5d996fb8s2cbed2765c4bf727@mail.gmail.com> Dear, Just create a custom partitioning layout with this structure ---- 1. first create a /boot partition from your primary(active) partition size between 100-500 MB. 2.now create a / i.e. a root partition in your extended partition 3. if required create a swap partition. now install fedora .it will work . From narendra.sisodiya at gmail.com Mon Oct 12 17:14:25 2009 From: narendra.sisodiya at gmail.com (narendra sisodiya) Date: Mon, 12 Oct 2009 22:44:25 +0530 Subject: [fedora-india] Request for media In-Reply-To: References: Message-ID: How can I get free Fedora CD/DVDs ? I want to distribute them in my workshops -- ??????????????????????????? ? Narendra Sisodiya ( ???????? ???????? ) ? Web : http://narendra.techfandu.org ? Twitter : http://tinyurl.com/dz7e4a ??????????????????????????? From thinklinux.ssh at gmail.com Mon Oct 12 20:24:10 2009 From: thinklinux.ssh at gmail.com (susmit shannigrahi) Date: Tue, 13 Oct 2009 01:54:10 +0530 Subject: [fedora-india] Indian FreeMedia contributors, you are yet to take up any freemedia request. Message-ID: Hi, I am feeling very low to remind time and again that most of us (Indian contributors) are not taking any freemedia requests. The minimum liability is 2 medias/month, which, if sent by ordinary post, never exceeds 50 INR. Given the minuscule amount involved, it is not a question of affordability, is it? If you can afford half an hour and 50 INR, it can be easily done. The list below is of every freemedia contributors from India. If you find yourself here, you agreed to send atleast two media/month. So please do contribute at least what you agreed to. We have only 88 pending requests, so if we take two requests each, it can be fulfilled very easily. Also, many of you have made generous contributions in the past (and doing at present). Our heartiest thanks for it. We are hoping for your contribution in future again. Thanks. --------------------------------------------------------------------------------------------------- 1 Anirudh Singh Shekhawat acedip AT fedoraproject DOT org 2 A. Mani amani AT fedoraproject DOT org 3 Amit Kumar Samsukha amitsamsukha AT fedoraproject DOT org 4 anirban chakrabarty anirbanchakrabarty AT fedoraproject DOT org 5 Ankur Sinha ankursinha AT fedoraproject DOT org 6 Ansar Ahmad ansarrehbar AT fedoraproject DOT org 7 Amit Pundir buggz AT fedoraproject DOT org 8 Dipanjan Chakraborty chakrabortydipanjan AT fedoraproject DOT org 9 Deependra Singh Shekhawat deepsa AT fedoraproject DOT org 10 Jaspalsinh A. Chauhan hugsheals AT fedoraproject DOT org 11 Shinde Suresh Baban indosoft AT fedoraproject DOT org 12 Jatin Khatri jatin AT fedoraproject DOT org 13 Arasappan karuppavel karuppavel AT fedoraproject DOT org 14 Kishan Goyal kishan AT fedoraproject DOT org 15 Arindam Ghosh makghosh AT fedoraproject DOT org 16 Mehul Patel mehulp AT fedoraproject DOT org 17 chandan babu mwnnlin AT fedoraproject DOT org 18 Mohammad Naseem naseemgnu AT fedoraproject DOT org 19 Nilesh J. Vaghela nileshjvaghela AT fedoraproject DOT org 20 Nirmal Pathak nirmalpathak AT fedoraproject DOT org 21 Parijat Mukherjee parijatmohor AT fedoraproject DOT org 22 Anil Kumar P pinnaka AT fedoraproject DOT org 23 raj kumar gajavelly rajgaja AT fedoraproject DOT org 24 Rejy M Cyriac rejymc AT fedoraproject DOT org 25 Arijit Upadhyaya rikie AT fedoraproject DOT org 26 Arun SAG sagarun AT fedoraproject DOT org 27 Shambo Bose shambo AT fedoraproject DOT org 28 Rangeen Basu Roy Chowdhury sherry151 AT fedoraproject DOT org 29 Siddharth Upmanyu siddhart AT fedoraproject DOT org 30 Dhaval Soni sonidhaval AT fedoraproject DOT org 31 Gaurav Taywade sparshme5 AT fedoraproject DOT org 32 Sri Krsna Rajan P srikrsna AT fedoraproject DOT org 33 Varun Patial strider AT fedoraproject DOT org 34 Subhodip Biswas subhodip AT fedoraproject DOT org 35 sunil datta sunildatta AT fedoraproject DOT org 36 Susmit Shannigrahi susmit AT fedoraproject DOT org 37 Upendra Jariya ujariya AT fedoraproject DOT org 38 Vinay Yadav vinayras AT fedoraproject DOT org 39 vipul tiwari vipulstyle AT fedoraproject DOT org 40 ananthgs ananthgs AT fedoraproject DOT org 41 ashwinmuni ashwinmuni AT fedoraproject DOT org 42 dbpatankar dbpatankar AT fedoraproject DOT org 43 empoweringlinux empoweringlinux AT fedoraproject DOT org 44 rishikesh rishikesh AT fedoraproject DOT org 45 thejaydeep thejaydeep AT fedoraproject DOT org 46 venom007 venom007 AT fedoraproject DOT org 47 vijju vijju AT fedoraproject DOT org --------------------------------------------------------------------------------------------------- -- Regards, Susmit. ============================================= ssh 0x86DD170A http://www.fedoraproject.org/wiki/user:susmit ============================================= Sent from Calcutta, WB, India From thinklinux.ssh at gmail.com Mon Oct 12 20:43:39 2009 From: thinklinux.ssh at gmail.com (susmit shannigrahi) Date: Tue, 13 Oct 2009 02:13:39 +0530 Subject: [fedora-india] Request for media In-Reply-To: References: Message-ID: Vivek, Once you are in Kolkata, come down to Santoshpur(near Jadavpur). I can provide you with one. On Mon, Oct 12, 2009 at 10:44 PM, narendra sisodiya wrote: > How can I get free Fedora CD/DVDs ? I want to distribute them in my workshops Narendra, If you have a FAS account, please file a ticket here https://fedorahosted.org/fedora-india/ Please note, you need to mention details of your workshop there. please make sure, you read this: https://fedoraproject.org/wiki/User:Sankarshan/Questions before filing the ticket. Thanks. -- Regards, Susmit. ============================================= ssh 0x86DD170A http://www.fedoraproject.org/wiki/user:susmit ============================================= Sent from Calcutta, WB, India From boni.vivek at gmail.com Tue Oct 13 04:31:24 2009 From: boni.vivek at gmail.com (Vivek Shah) Date: Tue, 13 Oct 2009 10:01:24 +0530 Subject: [fedora-india] Request for media In-Reply-To: References: Message-ID: Hi Susmit, On Tue, Oct 13, 2009 at 2:13 AM, susmit shannigrahi wrote: > Vivek, > Once you are in Kolkata, come down to Santoshpur(near Jadavpur). > I can provide you with one. Thanks a lot for the help. Will ping you off list when I will in Kolkata. Regards, Vivek From skbohra123 at gmail.com Wed Oct 14 06:59:59 2009 From: skbohra123 at gmail.com (shreekant bohra) Date: Wed, 14 Oct 2009 12:29:59 +0530 Subject: [fedora-india] Fedora Goodies for FOSS event Message-ID: <3f7a9110910132359g76f1b840ybca7306ed474f011@mail.gmail.com> Hello everyone, I am Shree Kant Bohra from Engineering College Bikaner Rajasthan, a final year engineering student and a Google Summer of Code 2009 student for Sahana Disaster Management System. I am pleased to tell you that, we FOSS lovers at our college have planned a four days FOSS event from 28th - 31st October 2009. The motive behind this event is to get people engaged into Open Source development. Since the FOSS event is in parallel with a India level technical festival of our college, FOSS event will have around 350-400 students from all across India. Four day of FOSS event will include various sessions and hackfests about different Open Source projects including Sahana, NUI group, Mozilla Firefox, Joomla, Drupal, and Fedora. For all four days we have planned an Installfest, we will install various flavours of Linux on participants laptops and will provide them with CD/DVDs of various distros. Being a free of cost and totally students organized event, we are trying to generate funds for the event through industry support. If we get Fedora goodies for the event, to be distributed among participants, it would really be a good attraction. Please let me know, if it is possible and if yes what procedure to be followed. Cheers -- Shree Kant Bohra Let the Source be open Blog: insideme.geekybuddha.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From sundaram at fedoraproject.org Wed Oct 14 06:59:50 2009 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Wed, 14 Oct 2009 12:29:50 +0530 Subject: [fedora-india] Fedora Goodies for FOSS event In-Reply-To: <3f7a9110910132359g76f1b840ybca7306ed474f011@mail.gmail.com> References: <3f7a9110910132359g76f1b840ybca7306ed474f011@mail.gmail.com> Message-ID: <4AD576E6.4020505@fedoraproject.org> On 10/14/2009 12:29 PM, shreekant bohra wrote: > > If we get Fedora goodies for the event, to be distributed among > participants, it would really be a good attraction. Please let me know, > if it is possible and if yes what procedure to be followed. File a ticket at https://fedorahosted.org/fedora-india/ If you have any questions, let me know. Rahul From skbohra123 at gmail.com Wed Oct 14 07:34:28 2009 From: skbohra123 at gmail.com (shreekant bohra) Date: Wed, 14 Oct 2009 13:04:28 +0530 Subject: [fedora-india] Fedora Goodies for FOSS event In-Reply-To: <4AD576E6.4020505@fedoraproject.org> References: <3f7a9110910132359g76f1b840ybca7306ed474f011@mail.gmail.com> <4AD576E6.4020505@fedoraproject.org> Message-ID: <3f7a9110910140034n310ee556r95b6cc342f9b6f4c@mail.gmail.com> Hi Rahul Thanks for the pointer, I have just raised a ticket there. Nice to see something like this exist, it has made things so easier. Fedora rocks! ;) Cheers On Wed, Oct 14, 2009 at 12:29 PM, Rahul Sundaram wrote: > On 10/14/2009 12:29 PM, shreekant bohra wrote: > > > > > If we get Fedora goodies for the event, to be distributed among > > participants, it would really be a good attraction. Please let me know, > > if it is possible and if yes what procedure to be followed. > > File a ticket at > > https://fedorahosted.org/fedora-india/ > > If you have any questions, let me know. > > Rahul > > _______________________________________________ > Fedora-india mailing list > Fedora-india at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-india > -- Shree Kant Bohra Let the Source be open Blog: insideme.geekybuddha.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From sundaram at fedoraproject.org Wed Oct 14 07:34:19 2009 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Wed, 14 Oct 2009 13:04:19 +0530 Subject: [fedora-india] Fedora Goodies for FOSS event In-Reply-To: <3f7a9110910140034n310ee556r95b6cc342f9b6f4c@mail.gmail.com> References: <3f7a9110910132359g76f1b840ybca7306ed474f011@mail.gmail.com> <4AD576E6.4020505@fedoraproject.org> <3f7a9110910140034n310ee556r95b6cc342f9b6f4c@mail.gmail.com> Message-ID: <4AD57EFB.3090106@fedoraproject.org> On 10/14/2009 01:04 PM, shreekant bohra wrote: > Hi Rahul > > Thanks for the pointer, I have just raised a ticket there. Nice to see > something like this exist, it has made things so easier. Fedora rocks! ;) Please specify in the ticket what you need in more specific details. If you want media, how many do you want for example. Rahul From narendra.sisodiya at gmail.com Wed Oct 14 07:42:16 2009 From: narendra.sisodiya at gmail.com (narendra sisodiya) Date: Wed, 14 Oct 2009 13:12:16 +0530 Subject: [fedora-india] Fedora Goodies for FOSS event In-Reply-To: <3f7a9110910140034n310ee556r95b6cc342f9b6f4c@mail.gmail.com> References: <3f7a9110910132359g76f1b840ybca7306ed474f011@mail.gmail.com> <4AD576E6.4020505@fedoraproject.org> <3f7a9110910140034n310ee556r95b6cc342f9b6f4c@mail.gmail.com> Message-ID: On Wed, Oct 14, 2009 at 1:04 PM, shreekant bohra wrote: > Hi Rahul > > Thanks for the pointer, I have just raised a ticket there. Nice to see > something like this exist, it has made things so easier. Fedora rocks! ;) > > Cheers > That need login account. I forget the usename and now i am uable to reset password.. any help ?? > On Wed, Oct 14, 2009 at 12:29 PM, Rahul Sundaram > wrote: >> >> On 10/14/2009 12:29 PM, shreekant bohra wrote: >> >> > >> > If we get Fedora goodies for the event, to be distributed among >> > participants, it would really be a good attraction. Please let me know, >> > if it is possible and if yes what procedure to be followed. >> >> File a ticket at >> >> https://fedorahosted.org/fedora-india/ >> >> If you have any questions, let me know. >> >> Rahul >> >> _______________________________________________ >> Fedora-india mailing list >> Fedora-india at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-india > > > > -- > Shree Kant Bohra > Let the Source be open > Blog: insideme.geekybuddha.org > > _______________________________________________ > Fedora-india mailing list > Fedora-india at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-india > -- ??????????????????????????? ? Narendra Sisodiya ( ???????? ???????? ) ? Web : http://narendra.techfandu.org ? Twitter : http://tinyurl.com/dz7e4a ??????????????????????????? From sundaram at fedoraproject.org Wed Oct 14 08:20:40 2009 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Wed, 14 Oct 2009 13:50:40 +0530 Subject: [fedora-india] Fedora Goodies for FOSS event In-Reply-To: References: <3f7a9110910132359g76f1b840ybca7306ed474f011@mail.gmail.com> <4AD576E6.4020505@fedoraproject.org> <3f7a9110910140034n310ee556r95b6cc342f9b6f4c@mail.gmail.com> Message-ID: <4AD589D8.6050006@fedoraproject.org> On 10/14/2009 01:12 PM, narendra sisodiya wrote: > On Wed, Oct 14, 2009 at 1:04 PM, shreekant bohra wrote: >> Hi Rahul >> >> Thanks for the pointer, I have just raised a ticket there. Nice to see >> something like this exist, it has made things so easier. Fedora rocks! ;) >> >> Cheers >> > That need login account. I forget the usename and now i am uable to > reset password.. any help ?? Which email address did you use to register the username? The accounts with the name Narendra is the account system are the following. The account name is followed by the user. .fas narendra mether: narendrakumarh 'H Narendra Kumar' - taciturn 'Tejas Narendra Gadaria' - nardneran 'Narendran S' - narendrarajuk 'narendrarajuk' - imnarendra 'Narendra Kumar' - adhinaren 'Narendra Adhikari' - nmakkena 'Narendra M' - narendra 'Naredra (1 more message) Rahul From narendra.sisodiya at gmail.com Wed Oct 14 12:49:19 2009 From: narendra.sisodiya at gmail.com (narendra sisodiya) Date: Wed, 14 Oct 2009 18:19:19 +0530 Subject: [fedora-india] Fedora Goodies for FOSS event In-Reply-To: <4AD589D8.6050006@fedoraproject.org> References: <3f7a9110910132359g76f1b840ybca7306ed474f011@mail.gmail.com> <4AD576E6.4020505@fedoraproject.org> <3f7a9110910140034n310ee556r95b6cc342f9b6f4c@mail.gmail.com> <4AD589D8.6050006@fedoraproject.org> Message-ID: On Wed, Oct 14, 2009 at 1:50 PM, Rahul Sundaram wrote: > On 10/14/2009 01:12 PM, narendra sisodiya wrote: >> On Wed, Oct 14, 2009 at 1:04 PM, shreekant bohra wrote: >>> Hi Rahul >>> >>> Thanks for the pointer, I have just raised a ticket there. Nice to see >>> something like this exist, it has made things so easier. Fedora rocks! ;) >>> >>> Cheers >>> >> That need login account. I forget the usename and now i am uable to >> reset password.. any help ?? > > Which email address did you use to register the username? The accounts > with the name Narendra is the account system are the following. The > account name is followed by the user. > > .fas narendra I just tried to signup , after entering email id (narendra.sisodiya AT gmail.com) it says, "this email is already registerd , please use forget password", At forget password It ask for usename and email id. I do not know usename. > mether: narendrakumarh 'H Narendra Kumar' > - taciturn 'Tejas Narendra Gadaria' - > nardneran 'Narendran S' - narendrarajuk > 'narendrarajuk' - imnarendra 'Narendra > Kumar' - adhinaren 'Narendra Adhikari' > - nmakkena 'Narendra M' - > narendra 'Naredra (1 more message) > > > Rahul > > _______________________________________________ > Fedora-india mailing list > Fedora-india at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-india > -- ??????????????????????????? ? Narendra Sisodiya ( ???????? ???????? ) ? Web : http://narendra.techfandu.org ? Twitter : http://tinyurl.com/dz7e4a ??????????????????????????? From sundaram at fedoraproject.org Wed Oct 14 13:27:12 2009 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Wed, 14 Oct 2009 18:57:12 +0530 Subject: [fedora-india] Fedora Goodies for FOSS event In-Reply-To: References: <3f7a9110910132359g76f1b840ybca7306ed474f011@mail.gmail.com> <4AD576E6.4020505@fedoraproject.org> <3f7a9110910140034n310ee556r95b6cc342f9b6f4c@mail.gmail.com> <4AD589D8.6050006@fedoraproject.org> Message-ID: <4AD5D1B0.2030506@fedoraproject.org> On 10/14/2009 06:19 PM, narendra sisodiya wrote: > On Wed, Oct 14, 2009 at 1:50 PM, Rahul Sundaram > wrote: >> On 10/14/2009 01:12 PM, narendra sisodiya wrote: >>> On Wed, Oct 14, 2009 at 1:04 PM, shreekant bohra wrote: >>>> Hi Rahul >>>> >>>> Thanks for the pointer, I have just raised a ticket there. Nice to see >>>> something like this exist, it has made things so easier. Fedora rocks! ;) >>>> >>>> Cheers >>>> >>> That need login account. I forget the usename and now i am uable to >>> reset password.. any help ?? Ask in #fedora-admin irc channel or drop a mail to webmaster at fp.o Rahul From yogsin at gmail.com Thu Oct 15 13:50:13 2009 From: yogsin at gmail.com (yogendra singh) Date: Thu, 15 Oct 2009 19:20:13 +0530 Subject: [fedora-india] Indian FreeMedia contributors, you are yet to take up any freemedia request. In-Reply-To: References: Message-ID: <74854c580910150650w6e95edf5p39628d233a8851b@mail.gmail.com> Dear sushmit How i can participate actively in this program. suggest me the proper way to do it. Thanks On Tue, Oct 13, 2009 at 1:54 AM, susmit shannigrahi wrote: > Hi, > > I am feeling very low to remind time and again that most of us (Indian > contributors) are not taking any freemedia requests. > > The minimum liability is 2 medias/month, which, if sent by ordinary > post, never exceeds 50 INR. Given the minuscule amount involved, it is > not a question of affordability, is it? If you can afford half an hour > and 50 INR, it can be easily done. > > The list below is of every freemedia contributors from India. If you > find yourself here, you agreed to send atleast two media/month. So > please do contribute at least what you agreed to. We have only 88 > pending requests, so if we take two requests each, it can be fulfilled > very easily. > > Also, many of you have made generous contributions in the past (and > doing at present). Our heartiest thanks for it. > We are hoping for your contribution in future again. > > > > Thanks. > > > > --------------------------------------------------------------------------------------------------- > 1 ? ? ? Anirudh Singh Shekhawat acedip AT fedoraproject DOT org > 2 ? ? ? A. Mani amani AT fedoraproject DOT org > 3 ? ? ? Amit Kumar Samsukha ? ? amitsamsukha AT fedoraproject DOT org > 4 ? ? ? anirban chakrabarty ? ? anirbanchakrabarty AT fedoraproject DOT org > 5 ? ? ? Ankur Sinha ? ? ankursinha AT fedoraproject DOT org > 6 ? ? ? Ansar Ahmad ? ? ansarrehbar AT fedoraproject DOT org > 7 ? ? ? Amit Pundir ? ? buggz AT fedoraproject DOT org > 8 ? ? ? Dipanjan Chakraborty ? ?chakrabortydipanjan AT fedoraproject DOT org > 9 ? ? ? Deependra Singh Shekhawat ? ? ? deepsa AT fedoraproject DOT org > 10 ? ? ?Jaspalsinh A. Chauhan ? hugsheals AT fedoraproject DOT org > 11 ? ? ?Shinde Suresh Baban ? ? indosoft AT fedoraproject DOT org > 12 ? ? ?Jatin Khatri ? ?jatin AT fedoraproject DOT org > 13 ? ? ?Arasappan karuppavel ? ?karuppavel AT fedoraproject DOT org > 14 ? ? ?Kishan Goyal ? ?kishan AT fedoraproject DOT org > 15 ? ? ?Arindam Ghosh ? makghosh AT fedoraproject DOT org > 16 ? ? ?Mehul Patel ? ? mehulp AT fedoraproject DOT org > 17 ? ? ?chandan babu ? ?mwnnlin AT fedoraproject DOT org > 18 ? ? ?Mohammad Naseem naseemgnu AT fedoraproject DOT org > 19 ? ? ?Nilesh J. Vaghela ? ? ? nileshjvaghela AT fedoraproject DOT org > 20 ? ? ?Nirmal Pathak ? nirmalpathak AT fedoraproject DOT org > 21 ? ? ?Parijat Mukherjee ? ? ? parijatmohor AT fedoraproject DOT org > 22 ? ? ?Anil Kumar P ? ?pinnaka AT fedoraproject DOT org > 23 ? ? ?raj kumar gajavelly ? ? rajgaja AT fedoraproject DOT org > 24 ? ? ?Rejy M Cyriac ? rejymc AT fedoraproject DOT org > 25 ? ? ?Arijit Upadhyaya ? ? ? ?rikie AT fedoraproject DOT org > 26 ? ? ?Arun SAG ? ? ? ?sagarun AT fedoraproject DOT org > 27 ? ? ?Shambo Bose ? ? shambo AT fedoraproject DOT org > 28 ? ? ?Rangeen Basu Roy Chowdhury ? ? ?sherry151 AT fedoraproject DOT org > 29 ? ? ?Siddharth Upmanyu ? ? ? siddhart AT fedoraproject DOT org > 30 ? ? ?Dhaval Soni ? ? sonidhaval AT fedoraproject DOT org > 31 ? ? ?Gaurav Taywade ?sparshme5 AT fedoraproject DOT org > 32 ? ? ?Sri Krsna Rajan P ? ? ? srikrsna AT fedoraproject DOT org > 33 ? ? ?Varun Patial ? ?strider AT fedoraproject DOT org > 34 ? ? ?Subhodip Biswas subhodip AT fedoraproject DOT org > 35 ? ? ?sunil datta ? ? sunildatta AT fedoraproject DOT org > 36 ? ? ?Susmit Shannigrahi ? ? ?susmit AT fedoraproject DOT org > 37 ? ? ?Upendra Jariya ?ujariya AT fedoraproject DOT org > 38 ? ? ?Vinay Yadav ? ? vinayras AT fedoraproject DOT org > 39 ? ? ?vipul tiwari ? ?vipulstyle AT fedoraproject DOT org > 40 ? ?ananthgs ?ananthgs AT fedoraproject DOT org > 41 ? ?ashwinmuni ? ?ashwinmuni AT fedoraproject DOT org > 42 ? ?dbpatankar ? ? ? ?dbpatankar AT fedoraproject DOT org > 43 ? ?empoweringlinux ? empoweringlinux AT fedoraproject DOT org > 44 ? ?rishikesh rishikesh AT fedoraproject DOT org > 45 ? thejaydeep ? ? thejaydeep AT fedoraproject DOT org > 46 ? venom007 ? venom007 AT fedoraproject DOT org > 47 ? vijju ? ? ?vijju AT fedoraproject DOT org > --------------------------------------------------------------------------------------------------- > -- > Regards, > Susmit. > > ============================================= > ssh > 0x86DD170A > http://www.fedoraproject.org/wiki/user:susmit > ============================================= > Sent from Calcutta, WB, India > > _______________________________________________ > Fedora-india mailing list > Fedora-india at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-india > From thinklinux.ssh at gmail.com Fri Oct 16 16:46:32 2009 From: thinklinux.ssh at gmail.com (susmit shannigrahi) Date: Fri, 16 Oct 2009 22:16:32 +0530 Subject: [fedora-india] FOSS.IN CfP is out. Lets plan about it. Message-ID: Hi, The CfP for foss.in[1] is out[2]. This year we are looking forward to participate there in a way that is beneficial to Fedora, the Indian Community around Fedora and FOSS in general. We have already a page in place[3]. Let's start planning. We don't have much time left. All ideas, proposals, suggestions and questions are welcome. Thanks. [1] http://foss.in/ [2] http://foss.in/news/fossincfp-2009.html [3] https://fedoraproject.org/wiki/Foss_in_2009 -- Regards, Susmit. ============================================= ssh 0x86DD170A http://www.fedoraproject.org/wiki/user:susmit ============================================= From jsimon at fedoraproject.org Fri Oct 16 17:01:28 2009 From: jsimon at fedoraproject.org (Joerg Simon) Date: Fri, 16 Oct 2009 19:01:28 +0200 Subject: [fedora-india] Re: FOSS.IN CfP is out. Lets plan about it. In-Reply-To: References: Message-ID: <200910161901.44786.jsimon@fedoraproject.org> On Friday 16 October 2009 18:46:32 susmit shannigrahi wrote: > Hi, > > The CfP for foss.in[1] is out[2]. Thanks, i will try to catch up with max (we really should send him an invitation to come) and i will take care for one or two talks and submit the proposals latest during the next week! Thanks RahulSundaram, SusmitShannigrahi, KushalDas for taking care of the Event on https://fedoraproject.org/wiki/Foss_in_2009. Susmit will you contact the foss.in people for a booth or a project day - small dev-room, mini-fad ... cu Joerg -- Joerg (kital) Simon jsimon at fedoraproject.org http://fedoraproject.org/wiki/JoergSimon http://kitall.blogspot.com Key Fingerprint: 3691 0989 2DCA 58A2 8D1F 2CAC C823 558E 5B5B 5688 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: From sankarshan at fedoraproject.org Fri Oct 16 22:17:54 2009 From: sankarshan at fedoraproject.org (sankarshan) Date: Sat, 17 Oct 2009 03:47:54 +0530 Subject: [fedora-india] Re: FOSS.IN CfP is out. Lets plan about it. In-Reply-To: <200910161901.44786.jsimon@fedoraproject.org> References: <200910161901.44786.jsimon@fedoraproject.org> Message-ID: <35586fc00910161517u27982003mb2fdaad2004cc72f@mail.gmail.com> On Fri, Oct 16, 2009 at 10:31 PM, Joerg Simon wrote: > On Friday 16 October 2009 18:46:32 susmit shannigrahi wrote: >> Hi, >> >> The CfP for foss.in[1] is out[2]. > > Thanks, i will try to catch up with max (we really should send him an > invitation to come) and i will take care for one or two talks and submit the > proposals latest during the next week! > > Thanks RahulSundaram, SusmitShannigrahi, KushalDas for taking care of the > Event on https://fedoraproject.org/wiki/Foss_in_2009. Susmit will you contact > the foss.in people for a booth or a project day - small dev-room, mini-fad ... We have a number of folks in and around Bangalore. For example, Shakthi, Hiemanshu, Rangeen are the ones who come to mind. It would be good to have them chip in with their plans and expectations from a Fedora presence at FOSS.IN especially if we are considering a set of WorkOuts or, Workshops. -- sankarshan mukhopadhyay Sent from Pune, MH, India From shakthimaan at gmail.com Sat Oct 17 04:16:22 2009 From: shakthimaan at gmail.com (Shakthi Kannan) Date: Sat, 17 Oct 2009 09:46:22 +0530 Subject: [fedora-india] Re: FOSS.IN CfP is out. Lets plan about it. In-Reply-To: <35586fc00910161517u27982003mb2fdaad2004cc72f@mail.gmail.com> References: <200910161901.44786.jsimon@fedoraproject.org> <35586fc00910161517u27982003mb2fdaad2004cc72f@mail.gmail.com> Message-ID: Hi, --- On Sat, Oct 17, 2009 at 3:47 AM, sankarshan wrote: | We have a number of folks in and around Bangalore. For example, | Shakthi, Hiemanshu, Rangeen are the ones who come to mind. It would be | good to have them chip in with their plans and expectations from a | Fedora presence at FOSS.IN especially if we are considering a set of | WorkOuts or, Workshops. \-- No plans from my end. SK -- Shakthi Kannan http://www.shakthimaan.com From thinklinux.ssh at gmail.com Sat Oct 17 04:31:48 2009 From: thinklinux.ssh at gmail.com (susmit shannigrahi) Date: Sat, 17 Oct 2009 10:01:48 +0530 Subject: [fedora-india] Re: FOSS.IN CfP is out. Lets plan about it. In-Reply-To: References: <200910161901.44786.jsimon@fedoraproject.org> <35586fc00910161517u27982003mb2fdaad2004cc72f@mail.gmail.com> Message-ID: > No plans from my end. Would you mind formulate and proposing one? Thanks. -- Regards, Susmit. ============================================= ssh 0x86DD170A http://www.fedoraproject.org/wiki/user:susmit ============================================= From shakthimaan at gmail.com Sat Oct 17 04:36:41 2009 From: shakthimaan at gmail.com (Shakthi Kannan) Date: Sat, 17 Oct 2009 10:06:41 +0530 Subject: [fedora-india] Re: FOSS.IN CfP is out. Lets plan about it. In-Reply-To: References: <200910161901.44786.jsimon@fedoraproject.org> <35586fc00910161517u27982003mb2fdaad2004cc72f@mail.gmail.com> Message-ID: Hi, --- On Sat, Oct 17, 2009 at 10:01 AM, susmit shannigrahi wrote: | Would you mind formulate and proposing one? \-- I'd leave it to the delegates/attendees to formulate one. SK -- Shakthi Kannan http://www.shakthimaan.com From jsimon at fedoraproject.org Sat Oct 17 09:02:11 2009 From: jsimon at fedoraproject.org (Joerg Simon) Date: Sat, 17 Oct 2009 11:02:11 +0200 Subject: [fedora-india] Re: FOSS.IN CfP is out. Lets plan about it. In-Reply-To: References: Message-ID: <200910171102.15525.jsimon@fedoraproject.org> On Saturday 17 October 2009 06:36:41 Shakthi Kannan wrote: > I'd leave it to the delegates/attendees to formulate one. i am a bit confused - Shakthi in which role you will attend foss.in? cu Joerg -- Joerg (kital) Simon jsimon at fedoraproject.org http://fedoraproject.org/wiki/JoergSimon http://kitall.blogspot.com Key Fingerprint: 3691 0989 2DCA 58A2 8D1F 2CAC C823 558E 5B5B 5688 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: From shakthimaan at gmail.com Sat Oct 17 09:12:16 2009 From: shakthimaan at gmail.com (Shakthi Kannan) Date: Sat, 17 Oct 2009 14:42:16 +0530 Subject: [fedora-india] Re: FOSS.IN CfP is out. Lets plan about it. In-Reply-To: <200910171102.15525.jsimon@fedoraproject.org> References: <200910171102.15525.jsimon@fedoraproject.org> Message-ID: Hi, --- On Sat, Oct 17, 2009 at 2:32 PM, Joerg Simon wrote: | i am a bit confused - Shakthi in which role you will attend foss.in? \-- I am not attending the event. Regards, SK -- Shakthi Kannan http://www.shakthimaan.com From jsimon at fedoraproject.org Sat Oct 17 09:19:49 2009 From: jsimon at fedoraproject.org (Joerg Simon) Date: Sat, 17 Oct 2009 11:19:49 +0200 Subject: [fedora-india] Re: FOSS.IN CfP is out. Lets plan about it. In-Reply-To: References: <200910171102.15525.jsimon@fedoraproject.org> Message-ID: <200910171119.53145.jsimon@fedoraproject.org> On Saturday 17 October 2009 11:12:16 Shakthi Kannan wrote: > I am not attending the event. oh that is sad - i always wanted to meet the person who made this great presentations! cu Joerg -- Joerg (kital) Simon jsimon at fedoraproject.org http://fedoraproject.org/wiki/JoergSimon http://kitall.blogspot.com Key Fingerprint: 3691 0989 2DCA 58A2 8D1F 2CAC C823 558E 5B5B 5688 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: From sherry151 at gmail.com Sun Oct 18 16:48:25 2009 From: sherry151 at gmail.com (Rangeen Basu) Date: Sun, 18 Oct 2009 22:18:25 +0530 Subject: [fedora-india] Association with a startup in Bangalore Message-ID: Hi One startup in Bangalore wants to run all their computers (around 20) on Fedora and requires installation, configration and network setup support. Is there anyone in Bangalore with proper knowledge of configuring servers and a linux network? I might use the help. I can easily take care of the installation and basic configuration part but regarding server setup, I am not really an expert.. -- Regards Rangeen Basu Roy Chowdhury Fedora Ambassador sherry151 at gmail.com From sundaram at fedoraproject.org Mon Oct 19 05:19:39 2009 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Mon, 19 Oct 2009 10:49:39 +0530 Subject: [fedora-india] Planning to present in or attend FOSS.IN 2009? Message-ID: <4ADBF6EB.9040606@fedoraproject.org> Hi The call for proposals in out. The important dates are: --- Oct-2009 | Call for Participation and start of submissions 26-Oct-2009 | End of submissions proposals 31-Oct-2009 | List of accepted submissions published 15-Nov-2009 | Due date for final slides & talk materials 01-Dec-2009 | Conference begins --- As you can see, you only got a very short period for submitting a proposal for a talk/workshop/workout. We have a Fedora Project day proposed to the organizers. Details at https://fedoraproject.org/wiki/Foss_in_2009 We have a limited budget to sponsor participants. If you are planning to present or attend the event edit the wiki (with your Fedora account) and add in more details. Go to http://foss.in and register as a speaker following the directions in the website. If you have any questions, let me know. Rahul From shakthimaan at gmail.com Mon Oct 19 05:54:55 2009 From: shakthimaan at gmail.com (Shakthi Kannan) Date: Mon, 19 Oct 2009 11:24:55 +0530 Subject: [fedora-india] Re: FOSS.IN CfP is out. Lets plan about it. In-Reply-To: <200910171119.53145.jsimon@fedoraproject.org> References: <200910171102.15525.jsimon@fedoraproject.org> <200910171119.53145.jsimon@fedoraproject.org> Message-ID: Hi, --- On Sat, Oct 17, 2009 at 2:49 PM, Joerg Simon wrote: | oh that is sad - i always wanted to meet the person who made this great | presentations! \-- No worries. Yes, my attendance to national, international (un)conferences is very poor. I really appreciate the good work being done by F/OSS events in major cities, and my best wishes are always with them. But my focus/attention is on places that need F/OSS presence, and hence, I need to dedicate and spend enough time for them. If I have to sacrifice my time, visits to F/OSS events, I am willing to pay the price for it. I also hope the organizers understand what I am doing, and forgive me for that. It is a small world, so we will definitely meet in some (un)conference, some day for sure. Regards, SK -- Shakthi Kannan http://www.shakthimaan.com From jsimon at fedoraproject.org Mon Oct 19 10:18:31 2009 From: jsimon at fedoraproject.org (Joerg Simon) Date: Mon, 19 Oct 2009 12:18:31 +0200 Subject: [fedora-india] Association with a startup in Bangalore In-Reply-To: References: Message-ID: <200910191218.39695.jsimon@fedoraproject.org> On Sunday 18 October 2009 18:48:25 Rangeen Basu wrote: > Hi > One startup in Bangalore wants to run all their computers (around 20) > on Fedora and requires installation, configration and network setup > support. Is there anyone in Bangalore with proper knowledge of > configuring servers and a linux network? I might use the help. I can > easily take care of the installation and basic configuration part but > regarding server setup, I am not really an expert.. I am absolutely sure that there are people who can/will do this very easily. Even me, as not the deepest technical person would be able to do this without any preparation. So i think this can be done by our contributors in Bangalore and around. Btw. i would not use Fedora for Servers. Nobody will upgrade Servers every 13 month - and the argument they(startup company) do not care about security, is maybe good for them, but it is not good for Fedora when a old Fedora Server is abused - for the press still a Fedora System is abused. The Company should use CentOS for their servers it's the same family. But! I do not think we should help a business without get something back. Here in Europe we call that Community Consulting where we enable companies to work with and on Fedora - and there is the Fedora EMEA e.V. as legal entity - non profit organisation - where you can spend donations for Fedora. We use this money for events, fad, fudcon, swag. We can save some RedHat Money and we report all that to the Fedora Board. I know that things are different in India and maybe the law does not allow moneyflow to a private contributor, but maybe it is possible that the startup Company helps as a Fedora Contributor, as example - provides proper accomodation for Fedora Contributors for Meet up's like foss.in or provides SWAG or Booth Material or simply code ;) cu Joerg -- Joerg (kital) Simon jsimon at fedoraproject.org http://fedoraproject.org/wiki/JoergSimon http://kitall.blogspot.com Key Fingerprint: 3691 0989 2DCA 58A2 8D1F 2CAC C823 558E 5B5B 5688 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: From sherry151 at gmail.com Mon Oct 19 12:59:47 2009 From: sherry151 at gmail.com (Rangeen Basu) Date: Mon, 19 Oct 2009 18:29:47 +0530 Subject: [fedora-india] Association with a startup in Bangalore In-Reply-To: <200910191218.39695.jsimon@fedoraproject.org> References: <200910191218.39695.jsimon@fedoraproject.org> Message-ID: > Btw. i would not use Fedora for Servers. Nobody will upgrade Servers every 13 > month - and the argument they(startup company) do not care about security, is > maybe good for them, but it is not good for Fedora when a old Fedora Server is > abused - for the press still a Fedora System is abused. > The Company should use CentOS for their servers it's the same family. Understood and will be conveyed to them. > Here in Europe we call that Community Consulting where we enable companies to > work with and on Fedora - and there is the Fedora EMEA e.V. as legal entity - > non profit organisation - where you can spend donations for Fedora. We use this > money for events, fad, fudcon, swag. We can save some RedHat Money and ?we > report all that to the Fedora Board. I have talked to them and they have agreed to pay us some money which I plan to use for freemedia. I don't think that will be a problem legally. > Company helps as a Fedora Contributor, as example - provides proper > accomodation for Fedora Contributors for Meet up's like foss.in or provides They are extremely small now with very limited budget, but I will stay in touch with them and check if they can help in any way. Also I will let them know about FOSS.in and also know if they are interested to participate. -- Regards Rangeen Basu Roy Chowdhury Fedora Ambassador sherry151 at gmail.com From sundaram at fedoraproject.org Mon Oct 19 13:01:26 2009 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Mon, 19 Oct 2009 18:31:26 +0530 Subject: [fedora-india] Association with a startup in Bangalore In-Reply-To: References: <200910191218.39695.jsimon@fedoraproject.org> Message-ID: <4ADC6326.7040803@fedoraproject.org> On 10/19/2009 06:29 PM, Rangeen Basu wrote: > I have talked to them and they have agreed to pay us some money which > I plan to use for freemedia. I don't think that will be a problem > legally. We cannot accept money directly but if they are willing to share the cost and recoup any expenses, that is ok. Donations "in-kind" in other words. > Also I will let them know about FOSS.in and also know if they are > interested to participate. That would be good. Thanks for staying on top of this. Rahul From rajkarn88 at gmail.com Mon Oct 19 18:08:02 2009 From: rajkarn88 at gmail.com (Rajkarn Singh) Date: Mon, 19 Oct 2009 23:38:02 +0530 Subject: [fedora-india] Planning to present in or attend FOSS.IN 2009? In-Reply-To: <4ADBF6EB.9040606@fedoraproject.org> References: <4ADBF6EB.9040606@fedoraproject.org> Message-ID: On Mon, Oct 19, 2009 at 10:49 AM, Rahul Sundaram wrote: > Hi > > The call for proposals in out. The important dates are: > > --- > > Oct-2009 | Call for Participation and start of submissions > 26-Oct-2009 | End of submissions proposals > 31-Oct-2009 | List of accepted submissions published > 15-Nov-2009 | Due date for final slides & talk materials > 01-Dec-2009 | Conference begins > > --- > > As you can see, you only got a very short period for submitting a > proposal for a talk/workshop/workout. We have a Fedora Project day > proposed to the organizers. Details at > > https://fedoraproject.org/wiki/Foss_in_2009 > > We have a limited budget to sponsor participants. If you are planning > to present or attend the event edit the wiki (with your Fedora account) > and add in more details. Go to http://foss.in and register as a speaker > following the directions in the website. If you have any questions, let > me know. > > Rahul > > _______________________________________________ > Fedora-india mailing list > Fedora-india at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-india > I'd been thinking to attend the conference this year, but the dates are clashing with my end-semester examinations. Ahhh..... However, I'd be looking for other opportunities to meet with open source enthusiasts :) Regards, Rajkarn Singh, B. Tech. Final Year, NIT Hamirpur. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ashwin_man at yahoo.com Mon Oct 19 18:06:05 2009 From: ashwin_man at yahoo.com (Ashwin Mansinghka) Date: Mon, 19 Oct 2009 11:06:05 -0700 (PDT) Subject: [fedora-india] Association with a startup in Bangalore Message-ID: <626837.67707.qm@web57610.mail.re1.yahoo.com> On 19-Oct-09 6:29 PM, Rangeen Basu wrote: >> Btw. i would not use Fedora for Servers. Nobody will upgrade Servers every 13 >> month - and the argument they(startup company) do not care about security, is >> maybe good for them, but it is not good for Fedora when a old Fedora Server is >> abused - for the press still a Fedora System is abused. >> The Company should use CentOS for their servers it's the same family. >> > Understood and will be conveyed to them. > > I have a slightly different view.... Fedora is as good a server as CentOS or Debian or SUSE or...... Security is simply a frame of mind. In my opinion, Fedora provides a evolving security platform for such new starters, they can graduate to a high security levels from low levels of today. I am sure a choice of using Fedora for servers should be appreciated and encouraged and supported by this forum instead of showing a different path altogether. >> Here in Europe we call that Community Consulting where we enable companies to >> work with and on Fedora - and there is the Fedora EMEA e.V. as legal entity - >> non profit organisation - where you can spend donations for Fedora. We use this >> money for events, fad, fudcon, swag. We can save some RedHat Money and we >> report all that to the Fedora Board. >> > I have talked to them and they have agreed to pay us some money which > I plan to use for freemedia. I don't think that will be a problem > legally. > > If it was Kolkata, I would have offered free but limited support. I like helping people who want to use linux in a big way. I can help online (over internet). If costs of travel and accommodation can be paid for, I can travel for a few days to the courageous users of Fedora, to provide initial thrust and support and confidence building, and a little training. >> Company helps as a Fedora Contributor, as example - provides proper >> accomodation for Fedora Contributors for Meet up's like foss.in or provides >> > They are extremely small now with very limited budget, but I will stay > in touch with them and check if they can help in any way. > > Also I will let them know about FOSS.in and also know if they are > interested to participate. > > Everything starts small, the ones which make it big are those which make the right choices, however tough and challenging those choices may tun out to be. Best of Lucks. with Regards, ASHWIN Add whatever you love to the Yahoo! India homepage. Try now! http://in.yahoo.com/trynew From foss.mailinglists at gmail.com Tue Oct 20 00:17:49 2009 From: foss.mailinglists at gmail.com (sankarshan) Date: Tue, 20 Oct 2009 05:47:49 +0530 Subject: [fedora-india] Association with a startup in Bangalore In-Reply-To: <4ADC6326.7040803@fedoraproject.org> References: <200910191218.39695.jsimon@fedoraproject.org> <4ADC6326.7040803@fedoraproject.org> Message-ID: <35586fc00910191717g623b339en7e992af58ae0cc4b@mail.gmail.com> On Mon, Oct 19, 2009 at 6:31 PM, Rahul Sundaram wrote: > We cannot accept money directly but if they are willing to share the > cost and recoup any expenses, that is ok. Donations "in-kind" in other > words. Thanks to Susmit, there's an entry at "I want to contribute money to Fedora - how can I" -- sankarshan mukhopadhyay From amitpundir at ymail.com Tue Oct 20 05:24:47 2009 From: amitpundir at ymail.com (Amit Pundir) Date: Mon, 19 Oct 2009 22:24:47 -0700 (PDT) Subject: [fedora-india] Association with a startup in Bangalore In-Reply-To: <626837.67707.qm@web57610.mail.re1.yahoo.com> References: <626837.67707.qm@web57610.mail.re1.yahoo.com> Message-ID: <980763.32816.qm@web31803.mail.mud.yahoo.com> ______________________________ >From: Ashwin Mansinghka >To: fedora-india at redhat.com >Sent: Mon, 19 October, 2009 11:36:05 PM >Subject: Re: [fedora-india] Association with a startup in Bangalore >On 19-Oct-09 6:29 PM, Rangeen Basu wrote: >>> Btw. i would not use Fedora for Servers. Nobody will upgrade Servers every 13 >>> month - and the argument they(startup company) do not care about security, is >>> maybe good for them, but it is not good for Fedora when a old Fedora Server is >>> abused - for the press still a Fedora System is abused. >>> The Company should use CentOS for their servers it's the same family. >>> >> Understood and will be conveyed to them. >> >> > >I have a slightly different view.... Fedora is as good a server as >CentOS or Debian or SUSE or...... >Security is simply a frame of mind. In my opinion, Fedora provides a >evolving security platform >for such new starters, they can graduate to a high security levels from >low levels of today. >I am sure a choice of using Fedora for servers should be appreciated and >encouraged and >supported by this forum instead of showing a different path altogether. > We are also using fedora for as server and its working nicely. >>> Here in Europe we call that Community Consulting where we enable companies to >>> work with and on Fedora - and there is the Fedora EMEA e.V. as legal entity - >>> non profit organisation - where you can spend donations for Fedora. We use this >>> money for events, fad, fudcon, swag. We can save some RedHat Money and we >>> report all that to the Fedora Board. >>> >> I have talked to them and they have agreed to pay us some money which >> I plan to use for freemedia. I don't think that will be a problem >> legally. >> >> > i with my other friend can help these people, i am not sure what all things has to be done, yes i do have setup our college lab where we have some 70 machines two webservers backup using rsync , nat using iptables .. if i can get exact idea of the things to be done we can provide a helping hand, >If it was Kolkata, I would have offered free but limited support. I like >helping people who want to use linux >in a big way. I can help online (over internet). If costs of travel and >accommodation can be paid for, I can >travel for a few days to the courageous users of Fedora, to provide >initial thrust and support and confidence >building, and a little training. > as we have good support online, things can be done with help of each other. >>> Company helps as a Fedora Contributor, as example - provides proper >>> accomodation for Fedora Contributors for Meet up's like foss.in or provides >>> >> They are extremely small now with very limited budget, but I will stay >> in touch with them and check if they can help in any way. >> >> Also I will let them know about FOSS.in and also know if they are >> interested to participate. >> >> > >Everything starts small, the ones which make it big are those which make >the right choices, however >tough and challenging those choices may tun out to be. Best of Lucks. Amit Pundir Kormangala, Bangalore Now, send attachments up to 25MB with Yahoo! India Mail. Learn how. http://in.overview.mail.yahoo.com/photos From jsimon at fedoraproject.org Tue Oct 20 07:07:37 2009 From: jsimon at fedoraproject.org (Joerg Simon) Date: Tue, 20 Oct 2009 09:07:37 +0200 Subject: [fedora-india] Association with a startup in Bangalore In-Reply-To: <626837.67707.qm@web57610.mail.re1.yahoo.com> References: <626837.67707.qm@web57610.mail.re1.yahoo.com> Message-ID: <200910200907.40155.jsimon@fedoraproject.org> On Monday 19 October 2009 20:06:05 Ashwin Mansinghka wrote: > I have a slightly different view.... Fedora is as good a server as > CentOS or Debian or SUSE or...... absolutely, but Fedora only for 13 month ;) cu Joerg -- Joerg (kital) Simon jsimon at fedoraproject.org http://fedoraproject.org/wiki/JoergSimon http://kitall.blogspot.com Key Fingerprint: 3691 0989 2DCA 58A2 8D1F 2CAC C823 558E 5B5B 5688 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: From jsimon at fedoraproject.org Tue Oct 20 08:14:01 2009 From: jsimon at fedoraproject.org (Joerg Simon) Date: Tue, 20 Oct 2009 10:14:01 +0200 Subject: [fedora-india] Association with a startup in Bangalore In-Reply-To: <980763.32816.qm@web31803.mail.mud.yahoo.com> References: <626837.67707.qm@web57610.mail.re1.yahoo.com> <980763.32816.qm@web31803.mail.mud.yahoo.com> Message-ID: <200910201014.07509.jsimon@fedoraproject.org> On Tuesday 20 October 2009 07:24:47 Amit Pundir wrote: > We are also using fedora for as server and its working nicely. That is really interesting i heard that before, but only in cases where people were surprised by not getting updates shortly after they implemented fedora as server - or project managers who got fired by choosing fedora as a serverplatform. I know a larger project in Mozambique, where they prototyped Servers for an rollout of several 1000 Systems. The project was finished, what do you think how happy they were as they realised that the underlying prototype version - which was new at the beginning of the project - is end of life since more than a year? Out of question that Fedora is technicaly a good Serverplatform. How do you handle the short release cycle and how do you handle major changes in key-applications during the lifecycle? If i see that some people using outdated (and therefore unsecure) Versions on a server, i get a bit angry, because they harm the Fedora Project by putting Fedora's reputation in danger. A System which is old and not updated will get abused some day for sure - as wrote before, a abused Fedora System is not good for Fedora. If someone is willing to take the risk for his own business, i am fine with it. But if we recommend people Fedora as a Server Platform we should tell them - "You can use this Fedora Version only 13 month(in the best case)" "If you update your Fedora it could be, that things works differently after the update" There is nothing wrong in recommending CentOS which has updates for 5 years and backported Features. And if you can handle Fedora - as one of our downstreams and binary twin to rhel you can handle it as well. On some Events here in Europe we share our Booth with the centos people because we are one family. cu Joerg -- Joerg (kital) Simon jsimon at fedoraproject.org http://fedoraproject.org/wiki/JoergSimon http://kitall.blogspot.com Key Fingerprint: 3691 0989 2DCA 58A2 8D1F 2CAC C823 558E 5B5B 5688 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: From amitpundir at ymail.com Tue Oct 20 09:29:41 2009 From: amitpundir at ymail.com (Amit Pundir) Date: Tue, 20 Oct 2009 02:29:41 -0700 (PDT) Subject: [fedora-india] Association with a startup in Bangalore In-Reply-To: <200910201014.07509.jsimon@fedoraproject.org> References: <626837.67707.qm@web57610.mail.re1.yahoo.com> <980763.32816.qm@web31803.mail.mud.yahoo.com> <200910201014.07509.jsimon@fedoraproject.org> Message-ID: <272131.72359.qm@web31813.mail.mud.yahoo.com> ----- Original Message ---- > From: Joerg Simon > To: fedora-india at redhat.com > Sent: Tue, 20 October, 2009 1:44:01 PM > Subject: Re: [fedora-india] Association with a startup in Bangalore > > On Tuesday 20 October 2009 07:24:47 Amit Pundir wrote: > > We are also using fedora for as server and its working nicely. > > That is really interesting i heard that before, but only in cases where people > were surprised by not getting updates shortly after they implemented fedora as > server - or project managers who got fired by choosing fedora as a > serverplatform. > I know a larger project in Mozambique, where they prototyped Servers for an > rollout of several 1000 Systems. The project was finished, what do you think > how happy they were as they realised that the underlying prototype version - > which was new at the beginning of the project - is end of life since more than > a year? > > Out of question that Fedora is technicaly a good Serverplatform. > > How do you handle the short release cycle and how do you handle major changes > in key-applications during the lifecycle? > > If i see that some people using outdated (and therefore unsecure) Versions on > a server, i get a bit angry, because they harm the Fedora Project by putting > Fedora's reputation in danger. > > A System which is old and not updated will get abused some day for sure - as > wrote before, a abused Fedora System is not good for Fedora. > > If someone is willing to take the risk for his own business, i am fine with it. > But if we recommend people Fedora as a Server Platform we should tell them - > > "You can use this Fedora Version only 13 month(in the best case)" > "If you update your Fedora it could be, that things works differently after the > update" > > There is nothing wrong in recommending CentOS which has updates for 5 years > and backported Features. And if you can handle Fedora - as one of our > downstreams and binary twin to rhel you can handle it as well. On some Events > here in Europe we share our Booth with the centos people because we are one > family. All this work is for college, completely managed by MCA students here, we don't have any business risk and fear of getting fired ... Fedora Rocks We have some two small webservers we are using for our college work, and we always have a new batch every year to handle servers and lab, as we have few small applications for our internal use, so the 13 month OS always is good, we update to new fedora almost every year with regularly installing the updates. sometime it gives some pain when we shift to new OS because somethings break when we move to a step higher i remember when i upgraded php4 to php5 and many projects were not working . but again that gives chance of learning for the students.. Amit Pundir http://www.andromeda.nitc.ac.in/ http://www.fosscell.nitc.ac.in/ Yahoo! India has a new look. Take a sneak peek http://in.yahoo.com/trynew From jsimon at fedoraproject.org Tue Oct 20 09:50:26 2009 From: jsimon at fedoraproject.org (Joerg Simon) Date: Tue, 20 Oct 2009 11:50:26 +0200 Subject: [fedora-india] Association with a startup in Bangalore In-Reply-To: <272131.72359.qm@web31813.mail.mud.yahoo.com> References: <626837.67707.qm@web57610.mail.re1.yahoo.com> <200910201014.07509.jsimon@fedoraproject.org> <272131.72359.qm@web31813.mail.mud.yahoo.com> Message-ID: <200910201150.29759.jsimon@fedoraproject.org> On Tuesday 20 October 2009 11:29:41 Amit Pundir wrote: > but again that gives chance of > learning for the students.. understand! Fedora is indeed a good learning platform! As far as i remember this thread started with a call for help for a startup business. I just think we should be fair and give them the a proper recommendation to get a sustainable Infrastructure. cu Joerg -- Joerg (kital) Simon jsimon at fedoraproject.org http://fedoraproject.org/wiki/JoergSimon http://kitall.blogspot.com Key Fingerprint: 3691 0989 2DCA 58A2 8D1F 2CAC C823 558E 5B5B 5688 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: From thinklinux.ssh at gmail.com Tue Oct 20 09:56:39 2009 From: thinklinux.ssh at gmail.com (susmit shannigrahi) Date: Tue, 20 Oct 2009 15:26:39 +0530 Subject: [fedora-india] Association with a startup in Bangalore In-Reply-To: <200910201150.29759.jsimon@fedoraproject.org> References: <626837.67707.qm@web57610.mail.re1.yahoo.com> <200910201014.07509.jsimon@fedoraproject.org> <272131.72359.qm@web31813.mail.mud.yahoo.com> <200910201150.29759.jsimon@fedoraproject.org> Message-ID: > understand! Fedora is indeed a good learning platform! > > As far as i remember this thread started with a call for help for a startup > business. I just think we should be fair and give them the a proper > recommendation to get a sustainable Infrastructure. Indeed. Even Fedora Infrastructure does not use fedora for production servers. :) -- Regards, Susmit. ============================================= ssh 0x86DD170A http://www.fedoraproject.org/wiki/user:susmit ============================================= From sundaram at fedoraproject.org Tue Oct 20 14:03:26 2009 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Tue, 20 Oct 2009 19:33:26 +0530 Subject: [fedora-india] Fedora 12 Beta now available! Message-ID: <4ADDC32E.6000605@fedoraproject.org> Hi. -- Fedora is a leading edge, free and open source operating system that continues to deliver innovative features to many users, with a new release every six months. We have reached the Fedora 12 Beta, the last important development milestone of Fedora 12. Only critical bug fixes will be pushed as updates leading up to the general release of Fedora 12, scheduled to be released in mid-November. We invite you to join us and participate in making Fedora 12 a solid release by downloading, testing, and providing us your valuable feedback. http://fedoraproject.org/get-prerelease Of course, this is a beta release, some problems may still be lurking. Should you trip across one of them, be sure it gets fixed before release by reporting your discovery at: https://bugzilla.redhat.com/ Thank you! What's New in Fedora 12? * Optimized performance - All software packages on 32-bit (x86_32) architecture have been compiled for i686 systems with special optimization for Intel Atom processors used in many netbooks but without losing compatibility with the overwhelming majority of CPUs. There is a list of the rare CPUs which will no longer be supported. * Smaller and faster updates - In Fedora 11, the optional yum-presto plugin, developed by Fedora contributor Jonathan Dieter, reduced update size by transmitting only the changes in the updated packages. Now, the plugin is installed by default. Also, RPMs now use XZ rather than gzip for compression, providing smaller package sizes without the memory and CPU penalties associated with bzip2. This lets us fit more software into each Fedora image, and uses less space on mirrors, making their administrators' lives a little easier. Thanks to the Fedora infrastructure team for their work in generating delta RPMs. * NetworkManager broadband and other enhancements - NetworkManager, originally developed by Red Hat's Dan Williams, was introduced in Fedora 7 and has become the de facto network configuration solution for distributions everywhere. Enhancements to NetworkManager make both system-wide connections and mobile broadband connections easier than ever. Signal strength and network selection are available for choosing the best mobile broadband connection when you're on the road. Bluetooth PAN support offers a simple click through process to access the Internet from your mobile phone. NetworkManager can now configure always-on and static address connections directly from the desktop. PolicyKit integration has been added so configuration management can be done via central policy where needed. IPv6 support has also been improved. * Next-generation (Ogg) Theora video - For several years, Theora, the open and free format not encumbered by known patents has provided a way for freedom-loving users to share video. Fedora 12 includes the new Theora 1.1, which achieves near-H.264 quality, meeting the expectations of demanding users with crisp, vibrant media in both streaming and downloadable form. Thanks to the work of the Xiph.Org Foundation's Christopher "Monty" Montgomery, sponsored by Red Hat, other Xiph developers, and the contribution of Mozilla.org, Firefox 3.5 can deliver free media on the web out of the box, using the Theora video and Vorbis audio formats even better than the previous release of Fedora. * Graphics support improvements - Fedora 12 introduces experimental 3D support for AMD Radeon HD 2400 and later graphics cards. To try it out, install the mesa-dri-drivers-experimental package. On many cards, this support should allow desktop effects to be used. Kernel mode setting (KMS) support, which was introduced on AMD hardware in Fedora 10 and extended to Intel hardware in Fedora 11, is now extended to NVIDIA hardware as well, meaning the great majority of systems now benefit from the smooth, fully-graphical startup sequence made possible by KMS. The Fedora graphical startup sequence now works better on systems with multiple monitors. Also on multiple monitor systems, the desktop will now automatically be spread across all monitors by default, rather than having all monitors display the same output, including on NVIDIA chips (where multiple monitor spanning was not possible without manual configuration changes in Fedora 11). Systems with NVIDIA graphics chips also gain initial support for suspend and resume functionality via the default Nouveau driver. Initial support for the new DisplayPort display connector has been added for Intel graphics chips. Support for Nvidia and ATI systems is already under rapid development and will be included in the next release of Fedora. Thanks to the Red Hat Xorg team including Adam Jackson (X server), Kristian H?gsberg (Intel driver), Dave Airlie and Jerome Glisse (Radeon driver for AMD), and Ben Skeggs (Nouveau driver for NVIDIA). * Virtualization improvements - Not content with all the improvements in Fedora 11, we've kicked virtualization based on KVM up another notch in Fedora 12. There are extensive improvements in performance, management, resource sharing, and still more security enhancements. A new library (libguestfs) and an interactive tool (guestfish) are now available for directly accessing and modifying virtual machine disk images. * Automatic reporting of crashes and SELinux issues - Abrt, a tool to help non-power users report crashes to Bugzilla with a few mouse clicks, is now enabled by default. Abrt collects detailed information automatically and helps developers identify and resolve issues faster, improving the quality of individual upstream components and Fedora. The SELinux alert monitoring tool has also added the ability to report SELinux issues to Bugzilla quickly and easily with just a couple of clicks. * New Dracut initrd generation tool - Up until Fedora 11, the boot system (initial ram disk or initrd) used to boot Fedora was monolithic, very distribution specific and didn't provide much flexibility. This has been replaced with Dracut, an initial ram disk generation tool with an event-based framework designed to be distribution-independent thanks to the Dracut team including Harald Hoyer, Jeremy Katz, Dave Jones and many others. It has been also adopted by OLPC which uses Fedora; OLPC modules for Dracut are available in the Fedora repository. * PackageKit plugins - PackageKit now has a plugin which can install an appropriate package when a user tries to run a command from a missing package. Another new plugin allows installation of software packages from a web browser. Thanks to Red Hat's Richard Hughes and the PackageKit team. * Bluetooth on-demand - Bluetooth services are automatically started when needed and stopped 30 seconds after last device use, reducing initial startup time and resource use when Bluetooth is not in active use. Thanks to Red Hat's Bastien Nocera. * Moblin graphical interface for netbooks - The Moblin graphical interface and applications are fully integrated thanks to Peter Robinson, a Fedora Project volunteer, and others. To use it, just install the Moblin Desktop Environment package group using yum or the graphical software management tools, and choose Moblin from the login manager. A F12 Moblin Fedora Remix (installable Live CD) will also be available. * PulseAudio enhancements - Red Hat's Lennart Poettering and several others have made significant improvements to the PulseAudio system. Improved mixer logic makes volume control more fine-grained and reliable. Integration with the Rygel UPnP media server means you can stream audio directly from your system to any UPnP / DLNA client, such as a Playstation 3. Hotplug support has been made more intelligent, so if you configure a device as the default output for a stream, unplug that device -- causing the stream(s) to be moved to another output device -- and later replug it, the stream is moved back to the preferred device. Finally, Bluetooth audio support means pairing with any Bluetooth audio device makes it available for use through PulseAudio. * Lower process privileges - In order to mitigate the impact of security vulnerabilities, permissions have been hardened for many files and system directories and process privileges have been lowered for a number of core components that require super user privileges. Red Hat's Steve Grubb has developed a new library, libcap-ng, and integrated it into many core system components to improve the security of Fedora. * SELinux sandbox - It is now possible to confine applications' access to the system and run them in a secure sandbox that takes advantage of the sophisticated capabilities of SELinux. Dan Walsh, SELinux developer at Red Hat, explains the details at http://danwalsh.livejournal.com/31146.html * Open Broadcom firmware - The openfwwf open source Broadcom firmware is included by default. This means wireless networking will be available out of the box on some Broadcom chipsets. * Hybrid live images - The Live images provided in this release can be directly imaged onto a USB stick using dd (or any equivalent tool) to create bootable Live USB keys. The Fedora Live USB Creator for Windows and the livecd-tools for Fedora are still recommended for data persistence and non-destructive writes. Thanks to Jeremy Katz. * Better webcam support - While Fedora 11 improved webcam support, in Fedora 12 you can expect even better video quality, especially for less expensive webcams. Red Hat's Hans de Goede, developer of the libv4l library, has more details on his continuous upstream webcam support enhancements at http://hansdegoede.livejournal.com/6989.html. * GNOME 2.28 - The latest version of the GNOME desktop includes the lighter Gnote replacement for Tomboy as the default note application, and Empathy replaces Pidgin as the default instant messenger. The new volume control application, first seen in Fedora 11, has been improved to restore some of the popular functionality from earlier releases without making the interface too complex. * GNOME Shell preview - Fedora 12 includes an early version of GNOME Shell, which will become the default interface for GNOME 3.0 and beyond. To try it, install the gnome-shell package, and use the Desktop Effects configuration tool to enable it. It will only work correctly from the GNOME desktop environment, not others such as KDE or Xfce. This is a preview technology, and some video cards may not be supported. * KDE 4.3 - The new KDE features an updated "Air" theme and fully configurable keyboard shortcuts in Plasma, improved performance and new desktop effects in the window manager, a new bug reporting tool, and a configuration tool for the LIRC infra-red remote control system. * Cool new stuff for developers beginning with Eclipse Galileo, which includes more plugins than ever before. Perl 6 is now included, along with PHP 5.3. For Haskell developers, the Haskell Platform now provides a standardized set of libraries and tools. But one of the biggest changes for developers is that most of the nice new features of Fedora 12, from Bluetooth to WebCams is implemented through underlying libraries, and many of the improvements will be included simply by relinking your application. Also available in this release are SystemTap 1.0 for improved instrumenting and debugging of binaries, complete with Eclipse integration, and the newest NetBeans IDE for Java development. * Cool new stuff for sysadmins includes added functionality for clustered Samba services (including active/active configurations) over GFS2; and the ability to boot a cluster of Fedora systems from a single, shared root file system. * Multi-Pointer X - The update to X.Org server 1.7 introduces the X Input Extension version 2.0 (XI2), with much work contributed by Red Hat's Peter Hutterer. This extension provides a new client API for handling input devices and also Multi-Pointer X (MPX) functionality. MPX functionality allows X to cope with many inputs of arbitrary types simultaneously, a prerequisite for (among others) multitouch-based desktops and multi-user interaction on a single screen. This is low-level work that applications and desktop environments will incrementally take advantage of in future releases. More details are available in the Release Notes and in the XI2 tag of Peter Hutterer's blog at http://who-t.blogspot.com/search/label/xi2 A full feature list is available on the wiki at http://fedoraproject.org/wiki/Releases/12/FeatureList OK, go get it. You know you can't wait. http://fedoraproject.org/get-prerelease Draft release notes and guides for several languages are available at http://docs.fedoraproject.org/drafts.html -- Rahul -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 199 bytes Desc: not available URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: Attached Message Part URL: From thinklinux.ssh at gmail.com Wed Oct 21 04:04:30 2009 From: thinklinux.ssh at gmail.com (susmit shannigrahi) Date: Wed, 21 Oct 2009 09:34:30 +0530 Subject: [fedora-india] What do I do if I want to upgrade to F12 beta using yum? Message-ID: I know a fresh install is better. :) But I don't find it in the docs. -- Regards, Susmit. ============================================= ssh 0x86DD170A http://www.fedoraproject.org/wiki/user:susmit ============================================= Sent from Calcutta, WB, India From foss.mailinglists at gmail.com Wed Oct 21 04:17:25 2009 From: foss.mailinglists at gmail.com (sankarshan) Date: Wed, 21 Oct 2009 09:47:25 +0530 Subject: [fedora-india] What do I do if I want to upgrade to F12 beta using yum? In-Reply-To: References: Message-ID: <35586fc00910202117y658ceaf0q4861ae89211e02f1@mail.gmail.com> On Wed, Oct 21, 2009 at 9:34 AM, susmit shannigrahi wrote: > I know a fresh install is better. :) > But I don't find it in the docs. does indicate that a fresh install is a good idea -- sankarshan mukhopadhyay From thinklinux.ssh at gmail.com Wed Oct 21 04:21:04 2009 From: thinklinux.ssh at gmail.com (susmit shannigrahi) Date: Wed, 21 Oct 2009 09:51:04 +0530 Subject: [fedora-india] What do I do if I want to upgrade to F12 beta using yum? In-Reply-To: <35586fc00910202117y658ceaf0q4861ae89211e02f1@mail.gmail.com> References: <35586fc00910202117y658ceaf0q4861ae89211e02f1@mail.gmail.com> Message-ID: > > > does indicate that a fresh install is a good idea Thanks. -- Regards, Susmit. ============================================= ssh 0x86DD170A http://www.fedoraproject.org/wiki/user:susmit ============================================= Sent from Calcutta, WB, India From skbohra123 at gmail.com Wed Oct 21 05:01:58 2009 From: skbohra123 at gmail.com (shreekant bohra) Date: Wed, 21 Oct 2009 10:31:58 +0530 Subject: [fedora-india] What do I do if I want to upgrade to F12 beta using yum? In-Reply-To: References: <35586fc00910202117y658ceaf0q4861ae89211e02f1@mail.gmail.com> Message-ID: <3f7a9110910202201x266f88d1tf3c89b24a9dc20ad@mail.gmail.com> Hi I used 'preupgrade ' to upgrade from f9 to f11 it went well , smooth. You can try that also Cheers On Wed, Oct 21, 2009 at 9:51 AM, susmit shannigrahi < thinklinux.ssh at gmail.com> wrote: > > > > < > https://fedoraproject.org/wiki/Common_F12_bugs#Issues_when_upgrading_from_previous_releases > > > > does indicate that a fresh install is a good idea > > Thanks. > > -- > Regards, > Susmit. > > ============================================= > ssh > 0x86DD170A > http://www.fedoraproject.org/wiki/user:susmit > ============================================= > Sent from Calcutta, WB, India > > _______________________________________________ > Fedora-india mailing list > Fedora-india at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-india > -- Shree Kant Bohra Let the Source be open Blog: insideme.geekybuddha.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From sundaram at fedoraproject.org Wed Oct 21 05:01:18 2009 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Wed, 21 Oct 2009 10:31:18 +0530 Subject: [fedora-india] What do I do if I want to upgrade to F12 beta using yum? In-Reply-To: References: Message-ID: <4ADE959E.5040803@fedoraproject.org> On 10/21/2009 09:34 AM, susmit shannigrahi wrote: > I know a fresh install is better. :) > But I don't find it in the docs. https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum The basic command is # yum --disablerepo=* enablerepo=rawhide update --skip-broken Rahul From foss.mailinglists at gmail.com Wed Oct 21 06:24:16 2009 From: foss.mailinglists at gmail.com (sankarshan) Date: Wed, 21 Oct 2009 11:54:16 +0530 Subject: [fedora-india] Re: [Ambassadors] Request to arrange a workshop in Ramakrishna Mission Shilpamandira Computer Centre, Howrah/Kolkata, West Bengal, India. In-Reply-To: <192469fb0910202317v555bdd9p41a9348bcc3319e2@mail.gmail.com> References: <192469fb0910202317v555bdd9p41a9348bcc3319e2@mail.gmail.com> Message-ID: <35586fc00910202324t19a4bbacv14861c8746fab991@mail.gmail.com> I am keeping the contents of the mail intact since I put the fedora-india list in cc: A location (in terms of city etc) would help get other interested speakers etc. /sankarshan On Wed, Oct 21, 2009 at 11:47 AM, Subrata Dey wrote: > Ramakrishna Mission Shilpamandira Computer?Center?is interested to arrange a > workshop with Fedora on 7th Nov, 2009. > They contacted me as a Fedora Ambassador. I had been a student of the > institute also. > There program schedule is as follows. > 1. A brief about Fedora by some Fedora People. > 2. A technical discussion about MONO Project & Wine. > What can we do for them? > Waiting to hear back from all of you. > Thanks, > Subrata. -- sankarshan mukhopadhyay Sent from Westford, MA, United States From sankarshan at fedoraproject.org Wed Oct 21 06:44:08 2009 From: sankarshan at fedoraproject.org (sankarshan) Date: Wed, 21 Oct 2009 12:14:08 +0530 Subject: [fedora-india] Re: [Ambassadors] Request to arrange a workshop in Ramakrishna Mission Shilpamandira Computer Centre, Howrah/Kolkata, West Bengal, India. In-Reply-To: <35586fc00910202324t19a4bbacv14861c8746fab991@mail.gmail.com> References: <192469fb0910202317v555bdd9p41a9348bcc3319e2@mail.gmail.com> <35586fc00910202324t19a4bbacv14861c8746fab991@mail.gmail.com> Message-ID: <35586fc00910202344l27227481hbd22c80eef0f1681@mail.gmail.com> On Wed, Oct 21, 2009 at 11:54 AM, sankarshan wrote: > I am keeping the contents of the mail intact since I put the > fedora-india list in cc: > > A location (in terms of city etc) would help get other interested speakers etc. > On Wed, Oct 21, 2009 at 11:47 AM, Subrata Dey wrote: > >> Ramakrishna Mission Shilpamandira Computer?Center?is interested to arrange a >> workshop with Fedora on 7th Nov, 2009. >> They contacted me as a Fedora Ambassador. I had been a student of the >> institute also. >> There program schedule is as follows. >> 1. A brief about Fedora by some Fedora People. >> 2. A technical discussion about MONO Project & Wine. Duh ! My mistake. Should have read the $subject more carefully. Would anyone from Kolkata/Howrah be interested in getting involved in this ? I am a bit wary about getting into a discussion about Mono and Wine right after introduction to Fedora. I'd perhaps like to see a bit more about how to participate in Fedora, talking about the upcoming F12 release before one goes into a discussion around Mono (if at all). To reiterate, is the URL to be bookmarked for presentations. Some idea about the expected audience might also help interested speakers. /sankarshan -- sankarshan mukhopadhyay Sent from Westford, MA, United States From thinklinux.ssh at gmail.com Wed Oct 21 07:10:43 2009 From: thinklinux.ssh at gmail.com (susmit shannigrahi) Date: Wed, 21 Oct 2009 12:40:43 +0530 Subject: [fedora-india] Re: [Ambassadors] Request to arrange a workshop in Ramakrishna Mission Shilpamandira Computer Centre, Howrah/Kolkata, West Bengal, India. In-Reply-To: <35586fc00910202344l27227481hbd22c80eef0f1681@mail.gmail.com> References: <192469fb0910202317v555bdd9p41a9348bcc3319e2@mail.gmail.com> <35586fc00910202324t19a4bbacv14861c8746fab991@mail.gmail.com> <35586fc00910202344l27227481hbd22c80eef0f1681@mail.gmail.com> Message-ID: >>> Ramakrishna Mission Shilpamandira Computer?Center?is interested to arrange a >>> workshop with Fedora on 7th Nov, 2009. > Duh ! My mistake. Should have read the $subject more carefully. Would > anyone from Kolkata/Howrah be interested in getting involved in this ? ! :) Subrata called me a bit earlier. I can/shall arrange things, though I shall not be able to get down there personally. > I am a bit wary about getting into a discussion about Mono and Wine > right after introduction to Fedora. I'd perhaps like to see a bit more > about how to participate in Fedora, And the alternative packages in Fedora to get things done. After all, everyone is concerned about getting things done at the end. Subrata, getting the list of packages that they use on a regular basis would be a good idea. > talking about the upcoming F12 > release before one goes into a discussion around Mono (if at all). Yes, if they insist. > To reiterate, is the > URL to be bookmarked for presentations. Some idea about the expected > audience might also help interested speakers. True. -- Regards, Susmit. ============================================= ssh 0x86DD170A http://www.fedoraproject.org/wiki/user:susmit ============================================= From thinklinux.ssh at gmail.com Thu Oct 22 05:17:14 2009 From: thinklinux.ssh at gmail.com (susmit shannigrahi) Date: Thu, 22 Oct 2009 10:47:14 +0530 Subject: [fedora-india] Packaging request - mwclient - a framework to MediaWiki's API. Message-ID: Hi, We are recently using mwclient[1] to automate the wiki updation. Unfortunately, there is no rpm package for it and hence we can not put the scripts up at infra. Can anyone please take it up? Thanks. [1] http://sourceforge.net/projects/mwclient/ -- Regards, Susmit. ============================================= ssh 0x86DD170A http://www.fedoraproject.org/wiki/user:susmit ============================================= Sent from Calcutta, WB, India From kushaldas at gmail.com Thu Oct 22 05:52:49 2009 From: kushaldas at gmail.com (Kushal Das) Date: Thu, 22 Oct 2009 11:22:49 +0530 Subject: [fedora-india] Packaging request - mwclient - a framework to MediaWiki's API. In-Reply-To: References: Message-ID: On Thu, Oct 22, 2009 at 10:47 AM, susmit shannigrahi wrote: > Hi, > > We are recently using mwclient[1] to automate the wiki updation. > Unfortunately, there is no rpm package for it and hence we can not put > the scripts up at infra. > > Can anyone please take it up? Review request at [1]. Already pushed to F11. [1] https://bugzilla.redhat.com/show_bug.cgi?id=523789 Kushal -- http://fedoraproject.org http://kushaldas.in From thinklinux.ssh at gmail.com Thu Oct 22 07:09:10 2009 From: thinklinux.ssh at gmail.com (susmit shannigrahi) Date: Thu, 22 Oct 2009 12:39:10 +0530 Subject: [fedora-india] Packaging request - mwclient - a framework to MediaWiki's API. In-Reply-To: References: Message-ID: > Review request at [1]. Already pushed to F11. oh..great. Thanks for pointing out. -- Regards, Susmit. ============================================= ssh 0x86DD170A http://www.fedoraproject.org/wiki/user:susmit ============================================= From sherry151 at gmail.com Thu Oct 22 07:18:18 2009 From: sherry151 at gmail.com (Rangeen Basu) Date: Thu, 22 Oct 2009 12:48:18 +0530 Subject: [fedora-india] Association with a startup in Bangalore In-Reply-To: <4ADC6326.7040803@fedoraproject.org> References: <200910191218.39695.jsimon@fedoraproject.org> <4ADC6326.7040803@fedoraproject.org> Message-ID: On Mon, Oct 19, 2009 at 6:31 PM, Rahul Sundaram > > We cannot accept money directly but if they are willing to share the > cost and recoup any expenses, that is ok. Donations "in-kind" in other > words. > The startup has sponsored 10 freemedias including postage which I will be sending out next week. I talked to them and they might want to become a resource centre as well. They are coming up with a website of their own and they might want to get listed as an offline vendor too. They might be interested to take part in FOSS.in as well but only as attendees. -- Regards Rangeen Basu Roy Chowdhury Fedora Ambassador sherry151 at gmail.com Sent from Bangalore, KA, India From kushaldas at gmail.com Thu Oct 22 09:18:35 2009 From: kushaldas at gmail.com (Kushal Das) Date: Thu, 22 Oct 2009 14:48:35 +0530 Subject: [fedora-india] Event report of IMPS Malda workshop Message-ID: Hi all, I just wrote a blog post on the workshop in IMPS Malda. You can read it here [1]. Photos can be found here [2]. [1] http://kushaldas.in/2009/10/22/fedora-workshop-in-imps-malda/ [2] http://www.flickr.com/photos/kushaldas/sets/72157622631345996/ Kushal -- http://fedoraproject.org http://kushaldas.in From thinklinux.ssh at gmail.com Thu Oct 22 09:35:36 2009 From: thinklinux.ssh at gmail.com (susmit shannigrahi) Date: Thu, 22 Oct 2009 15:05:36 +0530 Subject: [fedora-india] Packaging request - mwclient - a framework to MediaWiki's API. In-Reply-To: References: Message-ID: > oh..great. > Thanks for pointing out. I need a build against rhel 5 as the servers use it. Can you please check that? I don't have a koji login. -- Regards, Susmit. ============================================= ssh 0x86DD170A http://www.fedoraproject.org/wiki/user:susmit ============================================= Sent from Calcutta, WB, India From rakesh.pandit at gmail.com Thu Oct 22 09:45:10 2009 From: rakesh.pandit at gmail.com (Rakesh Pandit) Date: Thu, 22 Oct 2009 15:15:10 +0530 Subject: [fedora-india] Packaging request - mwclient - a framework to MediaWiki's API. In-Reply-To: References: Message-ID: 2009/10/22 susmit shannigrahi wrote: >> oh..great. >> Thanks for pointing out. > > I need a build against rhel 5 as the servers use it. ?Can you please check that? > I don't have a koji login. > [..] Will check with that and provide you off the list .. today late maybe. Catch me on channel. Thanks, -- Rakesh Pandit https://fedoraproject.org/ freedom, friends, features, first From thinklinux.ssh at gmail.com Thu Oct 22 09:45:57 2009 From: thinklinux.ssh at gmail.com (susmit shannigrahi) Date: Thu, 22 Oct 2009 15:15:57 +0530 Subject: [fedora-india] Packaging request - mwclient - a framework to MediaWiki's API. In-Reply-To: References: Message-ID: > Will check with that and provide you off the list .. today late maybe. > Catch me on channel. Thanks. -- Regards, Susmit. ============================================= ssh 0x86DD170A http://www.fedoraproject.org/wiki/user:susmit ============================================= Sent from Calcutta, WB, India From sundaram at fedoraproject.org Fri Oct 23 08:48:12 2009 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Fri, 23 Oct 2009 14:18:12 +0530 Subject: [fedora-india] Association with a startup in Bangalore In-Reply-To: References: <200910191218.39695.jsimon@fedoraproject.org> <4ADC6326.7040803@fedoraproject.org> Message-ID: <4AE16DCC.3030101@fedoraproject.org> On 10/22/2009 12:48 PM, Rangeen Basu wrote: > On Mon, Oct 19, 2009 at 6:31 PM, Rahul Sundaram > >> We cannot accept money directly but if they are willing to share the >> cost and recoup any expenses, that is ok. Donations "in-kind" in other >> words. >> > > The startup has sponsored 10 freemedias including postage which I will > be sending out next week. I talked to them and they might want to > become a resource centre as well. They are coming up with a website of > their own and they might want to get listed as an offline vendor too. > They might be interested to take part in FOSS.in as well but only as > attendees. As attendees is fine. Engaging in a conversation is always a helpful start. Rahul From debayanin at gmail.com Fri Oct 23 08:53:50 2009 From: debayanin at gmail.com (Debayan Banerjee) Date: Fri, 23 Oct 2009 14:23:50 +0530 Subject: [fedora-india] Association with a startup in Bangalore In-Reply-To: References: Message-ID: 2009/10/18 Rangeen Basu : > Hi > > One startup in Bangalore wants to run all their computers (around 20) > on Fedora and requires installation, configration and network setup > support. Is there anyone in Bangalore with proper knowledge of > configuring servers and a linux network? Vignesh and I will help you out. -- Regards, Debayan Banerjee Support Free Software http://deeproot.in From sundaram at fedoraproject.org Sat Oct 24 10:37:31 2009 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Sat, 24 Oct 2009 16:07:31 +0530 Subject: [fedora-india] Reminder: FOSS.IN 2009 26-Oct-2009 End of submissions proposals (23:59 GMT+0530) Message-ID: <4AE2D8EB.1010908@fedoraproject.org> Hi, If you are planning on proposing a talk as a speaker and haven't registered your talks at http://foss.in, now would be a good time to do so. If you are doing it as part of the proposed Fedora Project day, list your talk at https://fedoraproject.org/wiki/Foss_in_2009 Note that listing your talk in this wiki doesn't mean you are registered. You will have to register in the http://foss.in website directly. Thanks. Rahul From foss.mailinglists at gmail.com Mon Oct 26 09:33:08 2009 From: foss.mailinglists at gmail.com (sankarshan) Date: Mon, 26 Oct 2009 15:03:08 +0530 Subject: [fedora-india] Reminder: FOSS.IN 2009 26-Oct-2009 End of submissions proposals (23:59 GMT+0530) In-Reply-To: <4AE2D8EB.1010908@fedoraproject.org> References: <4AE2D8EB.1010908@fedoraproject.org> Message-ID: <35586fc00910260233y5ec37704m9c3155f2f06c1d3f@mail.gmail.com> On Sat, Oct 24, 2009 at 4:07 PM, Rahul Sundaram wrote: > If you are planning on proposing a talk as a speaker and haven't > registered your talks at http://foss.in, now would be a good time to do > so. If you are doing it as part of the proposed Fedora Project day, list > your talk at > > https://fedoraproject.org/wiki/Foss_in_2009 > > Note that listing your talk in this wiki doesn't mean you are > registered. You will have to register in the http://foss.in website > directly. Thanks. Once the FOSS.IN talk selection is over and, hopefully, a few of the proposals are accepted, would the folks like to huddle together on IRC or, telephone to plan things a bit more ? -- sankarshan mukhopadhyay Sent from Brisbane, CA, United States From sundaram at fedoraproject.org Mon Oct 26 09:39:01 2009 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Mon, 26 Oct 2009 15:09:01 +0530 Subject: [fedora-india] Reminder: FOSS.IN 2009 26-Oct-2009 End of submissions proposals (23:59 GMT+0530) In-Reply-To: <35586fc00910260233y5ec37704m9c3155f2f06c1d3f@mail.gmail.com> References: <4AE2D8EB.1010908@fedoraproject.org> <35586fc00910260233y5ec37704m9c3155f2f06c1d3f@mail.gmail.com> Message-ID: <4AE56E35.7000509@fedoraproject.org> On 10/26/2009 03:03 PM, sankarshan wrote: > Once the FOSS.IN talk selection is over and, hopefully, a few of the > proposals are accepted, would the folks like to huddle together on IRC > or, telephone to plan things a bit more ? Yes, as indicated in https://fedoraproject.org/wiki/Foss_in_2009. Susmit will lead the effort. Rahul From thinklinux.ssh at gmail.com Mon Oct 26 13:35:47 2009 From: thinklinux.ssh at gmail.com (susmit shannigrahi) Date: Mon, 26 Oct 2009 19:05:47 +0530 Subject: [fedora-india] Reminder: FOSS.IN 2009 26-Oct-2009 End of submissions proposals (23:59 GMT+0530) In-Reply-To: <4AE56E35.7000509@fedoraproject.org> References: <4AE2D8EB.1010908@fedoraproject.org> <35586fc00910260233y5ec37704m9c3155f2f06c1d3f@mail.gmail.com> <4AE56E35.7000509@fedoraproject.org> Message-ID: >> Once the FOSS.IN talk selection is over and, hopefully, a few of the >> proposals are accepted, would the folks like to huddle together on IRC >> or, telephone to plan things a bit more ? Yes, we would. Today I have submitted my workout. -- Regards, Susmit. ============================================= http://www.fedoraproject.org/wiki/user:susmit ============================================= Sent from Calcutta, WB, India From electromech at electromech.info Wed Oct 28 03:50:53 2009 From: electromech at electromech.info (ElectroMech) Date: Wed, 28 Oct 2009 09:20:53 +0530 Subject: [fedora-india] wireless Broadband (reliance and tata )setup - command line howto Message-ID: <24233aca0910272050x27367f02ybb431ce923412924@mail.gmail.com> Dear All, I have created small howto to connect wireless broadband Reliance and Tata with command line. So now you can use it with a linux which do not have GUI also. http://vglug.info/linux-rhel54-feroda-11-reliance-tata-wireless-broadband-command-line-howto -- -- Nilesh Vaghela ElectroMech Redhat Channel Partner and Training Partner 404, Maulik arcade, Above Karnavati Pagarakha Bazar, Nr. Mansi cross Road, Satellite Rd, Ahmedabad 25, The Emperor, Fatehgunj, Baroda. www.electromech.info -------------- next part -------------- An HTML attachment was scrubbed... URL: From rakesh.pandit at gmail.com Thu Oct 29 15:51:23 2009 From: rakesh.pandit at gmail.com (Rakesh Pandit) Date: Thu, 29 Oct 2009 21:21:23 +0530 Subject: [fedora-india] wireless Broadband (reliance and tata )setup - command line howto In-Reply-To: <24233aca0910272050x27367f02ybb431ce923412924@mail.gmail.com> References: <24233aca0910272050x27367f02ybb431ce923412924@mail.gmail.com> Message-ID: 2009/10/28 ElectroMech wrote: > Dear All, > > I have created small howto to connect wireless broadband Reliance and Tata > with command line. > > So now you can use it with a linux which do not have GUI also. > > http://vglug.info/linux-rhel54-feroda-11-reliance-tata-wireless-broadband-command-line-howto > [..] I searched this funda 2 years ago and found enough reference to material. Gone are days when I used to use wvdialconf to generate conf file and wvdial to connect to network. (Also do some hack (stupid mode = 1)). Times have changed and we have Network Manager since ages now. It would make sense to mention that ... but I guess it is so easy to configure wireless with Network Manager that you don't really need steps. -- Rakesh Pandit https://fedoraproject.org/ freedom, friends, features, first From steve at lonetwin.net Thu Oct 29 17:10:44 2009 From: steve at lonetwin.net (steve) Date: Thu, 29 Oct 2009 22:40:44 +0530 Subject: [fedora-india] wireless Broadband (reliance and tata )setup - command line howto In-Reply-To: References: <24233aca0910272050x27367f02ybb431ce923412924@mail.gmail.com> Message-ID: <4AE9CC94.8020601@lonetwin.net> Hi, On 10/29/2009 09:21 PM, Rakesh Pandit wrote: > 2009/10/28 ElectroMech wrote: >> Dear All, >> >> I have created small howto to connect wireless broadband Reliance and Tata >> with command line. >> >> So now you can use it with a linux which do not have GUI also. >> >> http://vglug.info/linux-rhel54-feroda-11-reliance-tata-wireless-broadband-command-line-howto >> > [..] > > I searched this funda 2 years ago and found enough reference to material. > > Gone are days when I used to use wvdialconf to generate conf file and > wvdial to connect to network. (Also do some hack (stupid mode = 1)). > Times have changed and we have Network Manager since ages now. It > would make sense to mention that ... but I guess it is so easy to > configure wireless with Network Manager that you don't really need > steps. Not exactly. While it is true that we at Fedora are moving towards making NetworkManager as the only tool required for all things network related, there are cases where NetworkManager fails to recognize the device and configuring using wvdial is the only option. For instance in the case of the ZTE AC8710 EVDO card distributed for the reliance broadband+ plan. More info at the bz if submitted here: https://bugzilla.redhat.com/show_bug.cgi?id=515412 also ... https://bugzilla.redhat.com/buglist.cgi?component=NetworkManager&product=Fedora NM is great but it's just not where you claim it to be yet. So, yeah, docs like Nilesh's are still useful. cheers, - steve -- random non tech spiel: http://lonetwin.blogspot.com/ tech randomness: http://lonehacks.blogspot.com/ what i'm stumbling into: http://lonetwin.stumbleupon.com/ From josemanimala at gmail.com Thu Oct 29 19:05:38 2009 From: josemanimala at gmail.com (Jose M Manimala) Date: Thu, 29 Oct 2009 12:05:38 -0700 Subject: [fedora-india] Re: fedora project In-Reply-To: <8fb108e00910290502r6336344fhf0570ea0e5f9dc33@mail.gmail.com> References: <8fb108e00910290502r6336344fhf0570ea0e5f9dc33@mail.gmail.com> Message-ID: <4AE9E782.2050907@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 KHILESH CHAUHAN wrote: > Best wishes sir, > My self khilesh chauhan from bhilai (chhattisgarh) > Currently doing B.E. in I.T. 3rd semester. > I want to join fedora project as a contributar as well as web developer > May you please help me ? > To whom should i contact regarding this ? > Please help me > > Thank you sir, > > Hello Khilesh, call me jose. :) There are many ways to contribute to Fedora and the best place to start will be by looking at the join us page http://fedoraproject.org/wiki/Join If you want to contribute as a web development take a look at the websites team on Join page. Also take a look at the infrastructure and os developer roles. If you need anything more you can find the community on the irc server at irc.freenode.net on the #fedora and #fedora-india channel. The fedora india team mailing list is fedora-india at redhat.com, feel free to contact the list and we will be happy to help you on your way. :) Best Regards Jose M Manimala -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkrp54IACgkQ68U/vco3DlJVkQCfeLHguaJgGIwcpPFyLgg3+r7q DHAAn2eXKF1CphVR3B7HHCQq1DqDj+R5 =n6GQ -----END PGP SIGNATURE----- From sankarshan.mukhopadhyay at gmail.com Fri Oct 30 05:59:27 2009 From: sankarshan.mukhopadhyay at gmail.com (sankarshan) Date: Fri, 30 Oct 2009 11:29:27 +0530 Subject: [fedora-india] A packaging request Message-ID: <7e3d3af30910292259j146efdd7kc1285ccebabd8d2f@mail.gmail.com> Would anyone be interested in packaging and maintaining wtop in Fedora ? -- sankarshan mukhopadhyay Sent from Brisbane, CA, United States From thinklinux.ssh at gmail.com Fri Oct 30 06:09:23 2009 From: thinklinux.ssh at gmail.com (susmit shannigrahi) Date: Fri, 30 Oct 2009 11:39:23 +0530 Subject: [fedora-india] Extending membership map for other groups. Message-ID: Hi, The membership map which was only for ambassadors so far can now easily be extended to any FAS group. Have a look here: https://fedoraproject.org/membership-map/index.html If you want map of a particular group, let me know. I remember Rahul wanted packager membership-map. Is that request stiil in place? Thanks. -- Regards, Susmit. ============================================= http://www.fedoraproject.org/wiki/user:susmit ============================================= Sent from Calcutta, WB, India From kushaldas at gmail.com Fri Oct 30 06:19:03 2009 From: kushaldas at gmail.com (Kushal Das) Date: Fri, 30 Oct 2009 11:49:03 +0530 Subject: [fedora-india] A packaging request In-Reply-To: <7e3d3af30910292259j146efdd7kc1285ccebabd8d2f@mail.gmail.com> References: <7e3d3af30910292259j146efdd7kc1285ccebabd8d2f@mail.gmail.com> Message-ID: On Fri, Oct 30, 2009 at 11:29 AM, sankarshan wrote: > Would anyone be interested in packaging and maintaining wtop > in Fedora ? Done in [1] [1] https://bugzilla.redhat.com/show_bug.cgi?id=531987 Kushal -- http://fedoraproject.org http://kushaldas.in From foss.mailinglists at gmail.com Fri Oct 30 06:24:10 2009 From: foss.mailinglists at gmail.com (sankarshan) Date: Fri, 30 Oct 2009 11:54:10 +0530 Subject: [fedora-india] A packaging request In-Reply-To: References: <7e3d3af30910292259j146efdd7kc1285ccebabd8d2f@mail.gmail.com> Message-ID: <35586fc00910292324u7566aeb5k20f690234fa48843@mail.gmail.com> On Fri, Oct 30, 2009 at 11:49 AM, Kushal Das wrote: > On Fri, Oct 30, 2009 at 11:29 AM, sankarshan > wrote: >> Would anyone be interested in packaging and maintaining wtop >> in Fedora ? > Done in [1] > > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=531987 *That* was fast. Thank you :) -- sankarshan mukhopadhyay From electromech at electromech.info Fri Oct 30 12:04:11 2009 From: electromech at electromech.info (ElectroMech) Date: Fri, 30 Oct 2009 17:34:11 +0530 Subject: [fedora-india] wireless Broadband (reliance and tata )setup - command line howto In-Reply-To: References: <24233aca0910272050x27367f02ybb431ce923412924@mail.gmail.com> Message-ID: <24233aca0910300504t2cd74dabu9b511a7a671bf6ae@mail.gmail.com> Hi Mr. Rakesh Pandit, > I have created small howto to connect wireless broadband Reliance and Tata > > with command line. > > > > So now you can use it with a linux which do not have GUI also. > > > > > http://vglug.info/linux-rhel54-feroda-11-reliance-tata-wireless-broadband-command-line-howto > > > [..] > > I searched this funda 2 years ago and found enough reference to material. > Before two years really ?? There was no wireless broadband it was only wireless at lower speed. > > Gone are days when I used to use wvdialconf to generate conf file and > wvdial to connect to network. (Also do some hack (stupid mode = 1)). > Times have changed and we have Network Manager since ages now. It > would make sense to mention that ... but I guess it is so easy to > configure wireless with Network Manager that you don't really need > steps. > I agreed with you but perhaps you forget that the GUI is mostly limited for desktop users, as far as concern us, we do not use much GUI with server or we do not load at all GUI in almost all server. As wireless broadband has excellent speed around 3.1MBPS can be user on server also for some specific application like proxy etc. That case we do not have NetworkManager ?? We need to configure it with command line. My purpose is just sharing some information for which I got around 10-12 phone calls. > > -- > Rakesh Pandit > https://fedoraproject.org/ > freedom, friends, features, first > > Thanks -- -- Nilesh Vaghela ElectroMech Redhat Channel Partner and Training Partner 404, Maulik arcade, Above Karnavati Pagarakha Bazar, Nr. Mansi cross Road, Satellite Rd, Ahmedabad 25, The Emperor, Fatehgunj, Baroda. www.electromech.info -------------- next part -------------- An HTML attachment was scrubbed... URL: From foss.mailinglists at gmail.com Fri Oct 30 12:58:16 2009 From: foss.mailinglists at gmail.com (sankarshan) Date: Fri, 30 Oct 2009 18:28:16 +0530 Subject: [fedora-india] Extending membership map for other groups. In-Reply-To: References: Message-ID: <35586fc00910300558lf810703u700ccde13bc336cd@mail.gmail.com> On Fri, Oct 30, 2009 at 11:39 AM, susmit shannigrahi wrote: > The membership map which was only for ambassadors so far can now > easily be extended to any FAS group. > Have a look here: https://fedoraproject.org/membership-map/index.html Susmit, thanks for doing this. This is much appreciated. There is a sizeable portion of the country that seems to be bereft of Ambassadors. Is it because the location data is missing or, is it truly that we do not have Ambassadors ? > If you want map of a particular group, let me know. > I remember Rahul wanted packager membership-map. Is that request stiil in place? I have sent you a set of requested maps off-list. Would be looking forward to them. Would you be blogging about this as well ? -- sankarshan mukhopadhyay Sent from Brisbane, CA, United States From thinklinux.ssh at gmail.com Fri Oct 30 13:02:35 2009 From: thinklinux.ssh at gmail.com (susmit shannigrahi) Date: Fri, 30 Oct 2009 18:32:35 +0530 Subject: [fedora-india] Extending membership map for other groups. In-Reply-To: <35586fc00910300558lf810703u700ccde13bc336cd@mail.gmail.com> References: <35586fc00910300558lf810703u700ccde13bc336cd@mail.gmail.com> Message-ID: > Susmit, thanks for doing this. This is much appreciated. Thanks for the encouragement. :) > There is a > sizeable portion of the country that seems to be bereft of > Ambassadors. Is it because the location data is missing or, is it > truly that we do not have Ambassadors ? Truly, we don't have many ambassadors there. > I have sent you a set of requested maps off-list. Would be looking > forward to them. Would you be blogging about this as well ? Taking clues your suggestions, I have changed my plan a bit. I am working on auto-generating maps of each and every group as they comes up in the FAS. This will save me(or anyone) hassles of maintaining this. And the data can be used without my intervention. -- Regards, Susmit. ============================================= http://www.fedoraproject.org/wiki/user:susmit ============================================= Sent from Calcutta, WB, India From sanjay.ankur at gmail.com Sat Oct 31 06:54:11 2009 From: sanjay.ankur at gmail.com (Ankur Sinha) Date: Sat, 31 Oct 2009 12:24:11 +0530 Subject: [fedora-india] DVD writer troubles In-Reply-To: <4AC8927E.9090903@lonetwin.net> References: <1254500615.2630.27.camel@localhost> <4AC8927E.9090903@lonetwin.net> Message-ID: <1256972051.2708.9.camel@localhost> On Sun, 2009-10-04 at 17:48 +0530, steve wrote: I've tried a lot of things, from wodim, to braser, to k3b and havent got more that 15% of dvds burnt properly. Outa 5, only 1 burns properly. > I don't know about wodim, but here are some tips to narrow down the problem: > > a. Check that the ISO file you are trying to burn isn't corrupt. Quick way would > be to mount it: > $ mount -o loop -t iso9006 Fedora-11-i386-DVD.iso /mnt > $ ls /mnt > > ...if that works, do a shasum check: > http://fedoraproject.org/en/verify Checked.. twice, thrice.. :( > > b. If the ISO file is ok, try another tool like k3b or brasero (in fact, if I am > not mistaken, with an ISO file even a dd should work fine -- i remember doing > that a couple of times) > tried both brasero and k3b.. no difference.. just more additions to my waste dvd pile.. > c. If writing still fails, I'd suspect the media. Try blank media from a > different set /brand -- sometimes one just gets unlucky with bad quality media. > I've tried both sony and moserbaer (the only ones you get here) .. its too much of a coincidence if all the dvds i purchase end up bad :( > d. If all else fails report back here or on fedora-list. > > HTH, > cheers, > - steve > > [1] https://www.redhat.com/mailman/listinfo/fedora-list I've even tried a USB writer (which i purchased in case my laptop writer was broken). However, same results. The USB writer gets "offlined" as dmesg says. This is followed by "rejecting IO to dead device" ( i checked and /dev/sr1 no longer exists). Another wasted dvd. These are the logs from the latest failed burns: http://ankursinha.fedorapeople.org/temp.txt http://ankursinha.fedorapeople.org/brasero-session.log I used brasero this time. I can try more dvds with k3b and wodim and post results if you want, if that'll help set it right. FYI, dvds burn perfect on my vista (i use a dual boot), which saddens me further :(. -- regards, Ankur From sanjay.ankur at gmail.com Sat Oct 31 07:16:20 2009 From: sanjay.ankur at gmail.com (Ankur Sinha) Date: Sat, 31 Oct 2009 12:46:20 +0530 Subject: [fedora-india] DVD writer troubles In-Reply-To: <4AC8927E.9090903@lonetwin.net> References: <1254500615.2630.27.camel@localhost> <4AC8927E.9090903@lonetwin.net> Message-ID: <1256973380.2708.12.camel@localhost> hi, More info: This ones from wodim.. It burnt the entire thing and failed on "Fixating".. Sooo close :( wodim output[1] dmesg output[2] you'll notice the "offlined device" that i had mentioned here. [1] http://ankursinha.fedorapeople.org/temp [2] http://ankursinha.fedorapeople.org/temp1 I haven't yet posted to the fedora-list, (since I'm already posting here) -- regards, Ankur From sanjay.ankur at gmail.com Sat Oct 31 07:53:47 2009 From: sanjay.ankur at gmail.com (Ankur Sinha) Date: Sat, 31 Oct 2009 13:23:47 +0530 Subject: [fedora-india] DVD writer troubles In-Reply-To: <4AC8927E.9090903@lonetwin.net> References: <1254500615.2630.27.camel@localhost> <4AC8927E.9090903@lonetwin.net> Message-ID: <1256975627.2708.15.camel@localhost> hi, last mail with info, from the log watch: WARNING: Kernel Errors Present ACPI Error (psargs-0359): [ ...: 56 Time(s) ACPI Error (psparse-0537): ...: 56 Time(s) Buffer I/O error on device sr0, l ...: 24 Time(s) Buffer I/O error on device sr1, l ...: 44 Time(s) end_request: I/O error, dev sr0, sector ...: 24 Time(s) end_request: I/O error, dev sr1, sector ...: 44 Time(s) scsi 10:0:0:0: Device offlined - not ready after error recovery ...: 1 Time(s) scsi 9:0:0:0: Device offlined - not ready after error recovery ...: 1 Time(s) sr 11:0:0:0: Device offlined - not ready after error recovery ...: 1 Time(s) sr 4:0:0:0: [sr0] Sense Key : Medium Error [current] ...: 16 Time(s) sr 6:0:0:0: Device offlined - not ready after error recovery ...: 1 Time(s) sr 7:0:0:0: Device offlined - not ready after error recovery ...: 1 Time(s) sr 8:0:0:0: Device offlined - not ready after error recovery ...: 2 Time(s) sr0: CDROM (ioctl) error, command: Read T ...: 13 Time(s) sr: Sense Key : Medium Error [current] ...: 13 Time(s) Apologies for the sudden gush, I'll wait for response before adding more :) -- regards, Ankur From steve at lonetwin.net Sat Oct 31 08:09:43 2009 From: steve at lonetwin.net (steve) Date: Sat, 31 Oct 2009 13:39:43 +0530 Subject: [fedora-india] DVD writer troubles In-Reply-To: <1256973380.2708.12.camel@localhost> References: <1254500615.2630.27.camel@localhost> <4AC8927E.9090903@lonetwin.net> <1256973380.2708.12.camel@localhost> Message-ID: <4AEBF0C7.5090905@lonetwin.net> Hi Ankur, On 10/31/2009 12:46 PM, Ankur Sinha wrote: > hi, > > More info: > > This ones from wodim.. > > It burnt the entire thing and failed on "Fixating".. Sooo close :( > Hmm, just curious did you try booting with this DVD ? Fixating a disk only means closing it off (I think it implies zeroing all remaining space on the disk). So, it *might* be possible that all relevant data has been written and the DVD is usable. I am just guessing here though. Another thought that occurred to me is that it is also possible that you need a firmware update for your drive. No kidding ! :). I've seen at least 3 instances of laptops that needed firmware updates for DVDs to work correctly. 2 dell model (D610 and D620) and my own lenovo Y410 (although when i purchased it the update was already applied). http://tinyurl.com/ybsouoe [Dell D610 update] http://tinyurl.com/ya8jjjo [Dell D620 update] http://consumersupport.lenovo.com/en/DriversDownloads/drivers_show_892.html I don't have any thoughts about your external sony writer tho'. I'd recommend that you check if firmware updates are available for your system, and apply them and if that does work or there aren't any, i'd recommend that you submit a bugzilla report describing your problem. cheers, - steve -- random non tech spiel: http://lonetwin.blogspot.com/ tech randomness: http://lonehacks.blogspot.com/ what i'm stumbling into: http://lonetwin.stumbleupon.com/ From sanjay.ankur at gmail.com Sat Oct 31 08:15:39 2009 From: sanjay.ankur at gmail.com (Ankur Sinha) Date: Sat, 31 Oct 2009 13:45:39 +0530 Subject: [fedora-india] DVD writer troubles In-Reply-To: <4AEBF0C7.5090905@lonetwin.net> References: <1254500615.2630.27.camel@localhost> <4AC8927E.9090903@lonetwin.net> <1256973380.2708.12.camel@localhost> <4AEBF0C7.5090905@lonetwin.net> Message-ID: <1256976939.2708.22.camel@localhost> On Sat, 2009-10-31 at 13:39 +0530, steve wrote: > Hi Ankur, > > On 10/31/2009 12:46 PM, Ankur Sinha wrote: > > hi, > > > > More info: > > > > This ones from wodim.. > > > > It burnt the entire thing and failed on "Fixating".. Sooo close :( > > > Hmm, just curious did you try booting with this DVD ? Fixating a disk only means > closing it off (I think it implies zeroing all remaining space on the disk). So, > it *might* be possible that all relevant data has been written and the DVD is > usable. I am just guessing here though. I've checked every dvd that's failed (hoping something was burnt). My system showed this latest one as a blank dvd :$ > > Another thought that occurred to me is that it is also possible that you need a > firmware update for your drive. No kidding ! :). > > I've seen at least 3 instances of laptops that needed firmware updates for DVDs > to work correctly. 2 dell model (D610 and D620) and my own lenovo Y410 (although > when i purchased it the update was already applied). > > http://tinyurl.com/ybsouoe [Dell D610 update] > http://tinyurl.com/ya8jjjo [Dell D620 update] > http://consumersupport.lenovo.com/en/DriversDownloads/drivers_show_892.html > I don't have any thoughts about your external sony writer tho'. > > I'd recommend that you check if firmware updates are available for your system, > and apply them and if that does work or there aren't any, i'd recommend that you > submit a bugzilla report describing your problem. > > cheers, > - steve > I'll check up on the firmware upgrade and post. However, since windows burns dvds properly, I think its unlikely that a firmware upgrade is needed. -- regards, Ankur From sanjay.ankur at gmail.com Sat Oct 31 08:24:15 2009 From: sanjay.ankur at gmail.com (Ankur Sinha) Date: Sat, 31 Oct 2009 13:54:15 +0530 Subject: [fedora-india] DVD writer troubles In-Reply-To: <4AEBF0C7.5090905@lonetwin.net> References: <1254500615.2630.27.camel@localhost> <4AC8927E.9090903@lonetwin.net> <1256973380.2708.12.camel@localhost> <4AEBF0C7.5090905@lonetwin.net> Message-ID: <1256977455.2708.26.camel@localhost> hi, Checked up on the product page[1] No firmware updates for the drive. What component should I file a bug against (kernel?)? Separate bugs for the inbuilt and the USB drives? Guess I'll have to boot into windows to burn *fedora* media till then. @Steve thank you for all your help. [1] http://h10025.www1.hp.com/ewfrf/wc/softwareList?os=2100&lc=en&dlc=en&cc=in&product=3398125&lang=en -- regards, Ankur From steve at lonetwin.net Sat Oct 31 09:05:24 2009 From: steve at lonetwin.net (steve) Date: Sat, 31 Oct 2009 14:35:24 +0530 Subject: [fedora-india] DVD writer troubles In-Reply-To: <1256977455.2708.26.camel@localhost> References: <1254500615.2630.27.camel@localhost> <4AC8927E.9090903@lonetwin.net> <1256973380.2708.12.camel@localhost> <4AEBF0C7.5090905@lonetwin.net> <1256977455.2708.26.camel@localhost> Message-ID: <4AEBFDD4.5060809@lonetwin.net> Hi Ankur, On 10/31/2009 01:54 PM, Ankur Sinha wrote: > hi, > > Checked up on the product page[1] > No firmware updates for the drive. > > What component should I file a bug against (kernel?)? Separate bugs for > the inbuilt and the USB drives? > I'd say start at application level first. File against one application and mention in your BZ that the problem is not app. specific. Let the developer make the call to escalate to the kernel. The kernel guys hate it when people just assume it is the kernel's fault without solid proof. By pointing out that is works on windows will make them even more angry :). In your case it looks like a kernel fault, but in many cases, it just happens that all userspace application eventually go through some userspace library which is at fault rather than the kernel. (For example bluetooth, usb devices which go through libusb etc) > Guess I'll have to boot into windows to burn *fedora* media till then. > Well, not necessarily. You do know that you can do installs from media on HDD too right ?[1] http://docs.fedoraproject.org/fedora-install-guide-en/fc4/sn-installing-from-harddrive.html Just copy the iso's to your windows partition (assuming it is FAT /not/ ntfs -- dunno the current status, but last i checked install from HDD supported only ext[23] and fat) > @Steve thank you for all your help. > No probs. cheers, - steve [1] If you didn't I betcha feeling just a little be like an id 10 t :) -- random non tech spiel: http://lonetwin.blogspot.com/ tech randomness: http://lonehacks.blogspot.com/ what i'm stumbling into: http://lonetwin.stumbleupon.com/ From steve at lonetwin.net Sat Oct 31 09:10:09 2009 From: steve at lonetwin.net (steve) Date: Sat, 31 Oct 2009 14:40:09 +0530 Subject: [fedora-india] DVD writer troubles In-Reply-To: <4AEBFDD4.5060809@lonetwin.net> References: <1254500615.2630.27.camel@localhost> <4AC8927E.9090903@lonetwin.net> <1256973380.2708.12.camel@localhost> <4AEBF0C7.5090905@lonetwin.net> <1256977455.2708.26.camel@localhost> <4AEBFDD4.5060809@lonetwin.net> Message-ID: <4AEBFEF1.4080504@lonetwin.net> On 10/31/2009 02:35 PM, steve wrote: > [...snip...] >> Guess I'll have to boot into windows to burn *fedora* media till then. >> > Well, not necessarily. You do know that you can do installs from media on HDD > too right ?[1] > http://docs.fedoraproject.org/fedora-install-guide-en/fc4/sn-installing-from-harddrive.html > Sorry, I just pasted the first google result. Here is the latest doc: http://docs.fedoraproject.org/install-guide/f11/en-US/html/s1-begininstall-hd-x86.html#table-Location_of_ISO_images cheers, - steve -- random non tech spiel: http://lonetwin.blogspot.com/ tech randomness: http://lonehacks.blogspot.com/ what i'm stumbling into: http://lonetwin.stumbleupon.com/ From electromech at electromech.info Sat Oct 31 09:40:05 2009 From: electromech at electromech.info (ElectroMech) Date: Sat, 31 Oct 2009 15:10:05 +0530 Subject: [fedora-india] DVD writer troubles In-Reply-To: <4AEBFEF1.4080504@lonetwin.net> References: <1254500615.2630.27.camel@localhost> <4AC8927E.9090903@lonetwin.net> <1256973380.2708.12.camel@localhost> <4AEBF0C7.5090905@lonetwin.net> <1256977455.2708.26.camel@localhost> <4AEBFDD4.5060809@lonetwin.net> <4AEBFEF1.4080504@lonetwin.net> Message-ID: <24233aca0910310240r2b24e35aoa952aa6fe39cd61@mail.gmail.com> Hi, Can you try following command to burn the dvd To use growisofs to write a pre-mastered ISO-image to a DVD: growisofs -dvd-compat -Z /dev/dvd=image.iso > >> Sorry, I just pasted the first google result. > Here is the latest doc: > > http://docs.fedoraproject.org/install-guide/f11/en-US/html/s1-begininstall-hd-x86.html#table-Location_of_ISO_images > > cheers, > - steve > > > Please let us know what happened. -- -- Nilesh Vaghela ElectroMech Redhat Channel Partner and Training Partner 404, Maulik arcade, Above Karnavati Pagarakha Bazar, Nr. Mansi cross Road, Satellite Rd, Ahmedabad 25, The Emperor, Fatehgunj, Baroda. www.electromech.info -------------- next part -------------- An HTML attachment was scrubbed... URL: From sanjay.ankur at gmail.com Sat Oct 31 10:01:52 2009 From: sanjay.ankur at gmail.com (Ankur Sinha) Date: Sat, 31 Oct 2009 15:31:52 +0530 Subject: [fedora-india] DVD writer troubles In-Reply-To: <4AEBFEF1.4080504@lonetwin.net> References: <1254500615.2630.27.camel@localhost> <4AC8927E.9090903@lonetwin.net> <1256973380.2708.12.camel@localhost> <4AEBF0C7.5090905@lonetwin.net> <1256977455.2708.26.camel@localhost> <4AEBFDD4.5060809@lonetwin.net> <4AEBFEF1.4080504@lonetwin.net> Message-ID: <1256983312.23770.1.camel@localhost> On Sat, 2009-10-31 at 14:40 +0530, steve wrote: > On 10/31/2009 02:35 PM, steve wrote: > > [...snip...] > >> Guess I'll have to boot into windows to burn *fedora* media till then. > >> > > Well, not necessarily. You do know that you can do installs from media on HDD > > too right ?[1] > > http://docs.fedoraproject.org/fedora-install-guide-en/fc4/sn-installing-from-harddrive.html > > > Sorry, I just pasted the first google result. > Here is the latest doc: > http://docs.fedoraproject.org/install-guide/f11/en-US/html/s1-begininstall-hd-x86.html#table-Location_of_ISO_images > > cheers, > - steve > hi, I meant burn media to distribute in the LocalContact and Free media programmes ;) Luckily, i dont need to feel like an "id 10 t" :) -- regards, Ankur From ashwin_man at yahoo.com Sat Oct 31 10:35:01 2009 From: ashwin_man at yahoo.com (Ashwin Mansinghka) Date: Sat, 31 Oct 2009 03:35:01 -0700 (PDT) Subject: [fedora-india] DVD writer troubles Message-ID: <564523.37630.qm@web57607.mail.re1.yahoo.com> On 31-Oct-09 12:46 PM, Ankur Sinha wrote: > hi, > > More info: > > This ones from wodim.. > > It burnt the entire thing and failed on "Fixating".. Sooo close :( > > wodim output[1] > > dmesg output[2] > > you'll notice the "offlined device" that i had mentioned here. > > [1] http://ankursinha.fedorapeople.org/temp > > [2] http://ankursinha.fedorapeople.org/temp1 > > > I haven't yet posted to the fedora-list, (since I'm already posting > here) > > > > > > I have faced this issue in past. The problem is related to write access to the DVD / CD writer. The culprits to tackle here are "selinux" and "PolicyKit......" configurations to allow the access to write to the DVD / CD writer. Do a little legwork (finger work with keyboard) or come back and ask again :) with Regards, ASHWIN Yahoo! India has a new look. Take a sneak peek http://in.yahoo.com/trynew From sanjay.ankur at gmail.com Sat Oct 31 10:44:55 2009 From: sanjay.ankur at gmail.com (Ankur Sinha) Date: Sat, 31 Oct 2009 16:14:55 +0530 Subject: [fedora-india] DVD writer troubles In-Reply-To: <24233aca0910310240r2b24e35aoa952aa6fe39cd61@mail.gmail.com> References: <1254500615.2630.27.camel@localhost> <4AC8927E.9090903@lonetwin.net> <1256973380.2708.12.camel@localhost> <4AEBF0C7.5090905@lonetwin.net> <1256977455.2708.26.camel@localhost> <4AEBFDD4.5060809@lonetwin.net> <4AEBFEF1.4080504@lonetwin.net> <24233aca0910310240r2b24e35aoa952aa6fe39cd61@mail.gmail.com> Message-ID: <1256985895.23770.6.camel@localhost> On Sat, 2009-10-31 at 15:10 +0530, ElectroMech wrote: > Hi, > > Can you try following command to burn the dvd > > To use growisofs to write a pre-mastered ISO-image to a DVD: > > growisofs -dvd-compat -Z /dev/dvd=image.iso > > > > Please let us know what happened. > > -- > -- > Nilesh Vaghela > ElectroMech > Redhat Channel Partner and Training Partner > 404, Maulik arcade, Above Karnavati Pagarakha Bazar, > Nr. Mansi cross Road, > Satellite Rd, Ahmedabad > 25, The Emperor, Fatehgunj, Baroda. > www.electromech.info hey! This one worked. Only for the laptop writer though. For the USB, it said : [Ankur at Ankur ~]$ growisofs -dvd-compat -Z /dev/sr1=/media/Winfuk/f11/Fedora-11-i386-DVD/Fedora-11-i386-DVD.iso :-( unable to open64("/dev/sr1",O_RDONLY): Permission denied I think installing "growisofs set-root-uid" as the man page says should work.. I'll try that. Thanks.. I can burn DVDs now. :D -- regards, Ankur From sanjay.ankur at gmail.com Sat Oct 31 10:47:47 2009 From: sanjay.ankur at gmail.com (Ankur Sinha) Date: Sat, 31 Oct 2009 16:17:47 +0530 Subject: [fedora-india] DVD writer troubles In-Reply-To: <564523.37630.qm@web57607.mail.re1.yahoo.com> References: <564523.37630.qm@web57607.mail.re1.yahoo.com> Message-ID: <1256986067.23770.9.camel@localhost> On Sat, 2009-10-31 at 03:35 -0700, Ashwin Mansinghka wrote: > On 31-Oct-09 12:46 PM, Ankur Sinha wrote: > > hi, > > > > More info: > > > > This ones from wodim.. > > > > It burnt the entire thing and failed on "Fixating".. Sooo close :( > > > > wodim output[1] > > > > dmesg output[2] > > > > you'll notice the "offlined device" that i had mentioned here. > > > > [1] http://ankursinha.fedorapeople.org/temp > > > > [2] http://ankursinha.fedorapeople.org/temp1 > > > > > > I haven't yet posted to the fedora-list, (since I'm already posting > > here) > > > > > > > > > > > > > I have faced this issue in past. > The problem is related to write access to the DVD / CD writer. > The culprits to tackle here are "selinux" and "PolicyKit......" > configurations > to allow the access to write to the DVD / CD writer. > > Do a little legwork (finger work with keyboard) or come back and ask > again :) > > with Regards, > ASHWIN Hey Ashwin, Can you please post the "legwork" needed? I really cant afford any more dvd burning try outs on a limited allowance.. :( I'd be extra grateful if you could please post *reasons* along with each step so I know exactly what I'm doing. (Knowing the path isn't enough, you should know why you're taking it too ;) ) -- regards, Ankur From steve at lonetwin.net Sat Oct 31 12:13:29 2009 From: steve at lonetwin.net (steve) Date: Sat, 31 Oct 2009 17:43:29 +0530 Subject: [fedora-india] DVD writer troubles In-Reply-To: <1256985895.23770.6.camel@localhost> References: <1254500615.2630.27.camel@localhost> <4AC8927E.9090903@lonetwin.net> <1256973380.2708.12.camel@localhost> <4AEBF0C7.5090905@lonetwin.net> <1256977455.2708.26.camel@localhost> <4AEBFDD4.5060809@lonetwin.net> <4AEBFEF1.4080504@lonetwin.net> <24233aca0910310240r2b24e35aoa952aa6fe39cd61@mail.gmail.com> <1256985895.23770.6.camel@localhost> Message-ID: <4AEC29E9.9010705@lonetwin.net> Hi, On 10/31/2009 04:14 PM, Ankur Sinha wrote: > On Sat, 2009-10-31 at 15:10 +0530, ElectroMech wrote: >> Hi, >> >> Can you try following command to burn the dvd >> >> To use growisofs to write a pre-mastered ISO-image to a DVD: >> >> growisofs -dvd-compat -Z /dev/dvd=image.iso >> >> > > > This one worked. Only for the laptop writer though. > > For the USB, it said : > > [Ankur at Ankur ~]$ growisofs -dvd-compat > -Z /dev/sr1=/media/Winfuk/f11/Fedora-11-i386-DVD/Fedora-11-i386-DVD.iso > :-( unable to open64("/dev/sr1",O_RDONLY): Permission denied > > I think installing "growisofs set-root-uid" as the man page says should > work.. I'll try that. > > Thanks.. I can burn DVDs now. :D Interesting to know growisofs worked but wodim didn't. I'd suggest you trace down the problem and/or file a bug against wodim and other apps that failed. So that they are able to handle whatever the problem was in the manner growisofs does or failing that, error out in a meaningful manner which would point to the source of the problem. As for the second error also file a bug against growisofs or debug it further and file a bug against the right component (most likely would turn out to be a problem with HAL or udev). I'd suggest getting a re-writeable CD/DVD media tho' :) cheers, - steve PS: Please *do* file a bug even if you aren't that much into debugging. Lack of bugs is what causes others to comment -- it works on windows but doesn't on linux. -- random non tech spiel: http://lonetwin.blogspot.com/ tech randomness: http://lonehacks.blogspot.com/ what i'm stumbling into: http://lonetwin.stumbleupon.com/ From sanjay.ankur at gmail.com Sat Oct 31 12:24:16 2009 From: sanjay.ankur at gmail.com (Ankur Sinha) Date: Sat, 31 Oct 2009 17:54:16 +0530 Subject: [fedora-india] DVD writer troubles In-Reply-To: <4AEC29E9.9010705@lonetwin.net> References: <1254500615.2630.27.camel@localhost> <4AC8927E.9090903@lonetwin.net> <1256973380.2708.12.camel@localhost> <4AEBF0C7.5090905@lonetwin.net> <1256977455.2708.26.camel@localhost> <4AEBFDD4.5060809@lonetwin.net> <4AEBFEF1.4080504@lonetwin.net> <24233aca0910310240r2b24e35aoa952aa6fe39cd61@mail.gmail.com> <1256985895.23770.6.camel@localhost> <4AEC29E9.9010705@lonetwin.net> Message-ID: <1256991856.2712.8.camel@localhost> On Sat, 2009-10-31 at 17:43 +0530, steve wrote: > Interesting to know growisofs worked but wodim didn't. I'd suggest you trace > down the problem and/or file a bug against wodim and other apps that failed. So > that they are able to handle whatever the problem was in the manner growisofs > does or failing that, error out in a meaningful manner which would point to the > source of the problem. > and not waste media!!! > As for the second error also file a bug against growisofs or debug it further > and file a bug against the right component (most likely would turn out to be a > problem with HAL or udev). > > I'd suggest getting a re-writeable CD/DVD media tho' :) its because the ACL of my USB drive does not contain "Ankur" as user laptop drive: [Ankur at Ankur ~]$ getfacl /dev/sr0 getfacl: Removing leading '/' from absolute path names # file: dev/sr0 # owner: root # group: cdrom user::rw- user:Ankur:rw- group::rw- mask::rw- other::--- USB drive: [Ankur at Ankur ~]$ getfacl /dev/sr1 getfacl: Removing leading '/' from absolute path names # file: dev/sr1 # owner: root # group: cdrom user::rw- user::rw- group::rw- mask::rw- other::--- Dont really think its a bug. Ill confirm with what the man page has to say before filing one for growisofs > > cheers, > - steve > > PS: Please *do* file a bug even if you aren't that much into debugging. Lack of > bugs is what causes others to comment -- it works on windows but doesn't on linux. Yeah, I will file bugs (wodim and brasero currently, maybe k3b once I waste a few dvds on that). I like bugzilla :) -- regards, Ankur From ashwin.lists at gmail.com Sat Oct 31 14:14:10 2009 From: ashwin.lists at gmail.com (Ashwin) Date: Sat, 31 Oct 2009 19:44:10 +0530 Subject: [fedora-india] DVD writer troubles In-Reply-To: <1256986067.23770.9.camel@localhost> References: <564523.37630.qm@web57607.mail.re1.yahoo.com> <1256986067.23770.9.camel@localhost> Message-ID: <4AEC4632.4040503@gmail.com> > Hey Ashwin, > > Can you please post the "legwork" needed? I really cant afford any more > dvd burning try outs on a limited allowance.. :( > > I'd be extra grateful if you could please post *reasons* along with each > step so I know exactly what I'm doing. (Knowing the path isn't enough, > you should know why you're taking it too ;) ) > > The minimum legwork is to read on the two mentioned points. The reading will not hit your allowances I hope. :) Reading, obviously you have to do for yourself for sure ;) Do a simple test - login as a regular user (non - root user) and insert a USB stick / drive, does it mount automatically ? If it does, great, or if you need to fix that, the same two points have to be dealt with, while dealing with the same, I am sure your eyes will see / spot the path / reason. The reason to know why to take a specific path, is to reach a desired destination. The doubt is (if any implied), "if it is the right or wrong path". Well, you need to walk at least a few steps to find it yourself. Others can only indicate the various paths to "nirvana" the reason for "nirvana" is same, but path to "nirvana differs for person to person. with Regards, ASHWIN