Posts Tagged ‘RHEL’

MondoRescue 3.2.1 is definitively looking better but will for sure with your help !

2015/03/06

Since a couple of days, I’ve passed quite some time to deal with the various reports that were made on the mondo mailing list with regards to bugs found by users on version 3.2.0. Of course, as every .0 version, not everything was tested, and the help of the community is as usual key to find these cases left appart, and of course find bugs in them !

What has been fixed is available here:
http://trac.mondorescue.org/query?status=closed&group=resolution&milestone=3.2.1

The other BRs I’d like to address before releasing 3.2.1 are:

  • glibc detect an invalid pointer (#766)
  • Smartarray b120i closed drivers not working (#751)

and the older, but really annoying one:

  • Fail to Restore from External Hard Disk (#628)

While I think I can deal with the 2 first one pretty easily, the last one requires more time and will probably end up in 3.2.2 instead, as it’s difficult to delay more 3.2.1 now that the most annoying issues have been solved.

In the mean time, please test the beta of 3.2.1 at ftp://ftp.mondorescue.org/test/ (lots of distros available). That will clearly help me finalizing that version. Hopefully you’ll mostly report successes, but I really need your help to make it much better than 3.2.0.

With the latest devs made on mindi to support again correctly older distributions such as RHEL5 (which wasn’t working anymore in 3.2.0), I think I’ll also being able to make the promised 3.0.5 soon, for those wanting to avoid the risk of using a mondoarchive very different in code with lots of dynamically allocated memory. That will pretty surely be the last one in that serie. The focus is really now on the 3.2 branch.

Thanks for your continuous support on this project !

Merry Christmas, MondoRescue 3.2.0 is out !

2014/12/24

My previous post was to announce I wanted to publish that long overdue 3.2.0 version of MondoRescue beofre Christmas, so here we are !

I finally found the issue I had restoring RHEL7 with 3.2.0. This was due to a cumul of problems:

  • XFS labelling was broken. I fixed it by calling appropriately xfs_admin in label-partitions-as-necessary
  • RHEL7 uses a UUID for / in the grub2 configuration, which is not mentioned in /etc/fstab; so mindi wasn’t recreating that UUID correctly. So now mindi will store in the mountlist.txt the UUID of each partition, if no other LABEL or UUID was explicitely given in /etc/fstab in order to be able to use it at restore time, and label-partitions-as-necessary was also updated to take that in account

And I was with these modifications able to restore fully automatically a RHEL7 VM. So as I had alrady a working RHEL6 and Fedora 20 env, and as no big regression is expected on other supported distros (Mageia, SLES, OpenSuSE, Debian, Ubuntu mainly) I thought it was time to deliver it officially and give you a toy to play with for Christmas ! Am I not a nice guy ;-) ?

A lot as changed with regards to 3.0.4. If you want to have all the details, look at the Changelogs available in the trac announce, or read my previous posts about the 3.2 branch development, which started back in October 2013 (or even before in fact).

Is it the end of the 3.0 branch ? No. As I announced it earlier already, I want to at least publish a 3.0.5 with most mindi modifications backported in it (SVN already has such a branch in fact) in order for those of you who don’t like major updates, to stay with a more stable branch for some months, before jumping into 3.2.x. Because 3.2.x is the future, and most of my development time will happen here.

Hopefully that 3.0.5 branch will also work fine with systemd and /usr only based distros as the modifications to support that have all been done in mindi.

As for the 3.2.x branch, please report your findings ! I know I’m far from answering all mails, or answer all bug reports, but I do rad all of these, and as time permit, I try to make the code evolve (typically adding more perl functions) to have a more flexible way of incorporating your requests. Slower, but I have an installed base to maintain, I’m not like Fedora, which will always be followed, I need to keep my sysadmin as happy as possible with the state of the tool, while maintaing as much compatibility as I can with the previous versions.

But all that won’t happen before early January, as I’ll pass time with my kids and my wife to celebrate Christmas, an enjoy being together, which is now not as often as the previous years (yes kids grow up and move sometimes far from home :-), and that’s good !)

As I write packages are still being delivered to the master ftp server. Try it after the 25th !

MondoRescue 3.2.0: last beta before publishing

2014/12/07

I’m probably far from being a good project leader. The lack of time is one of the reason, but I think I could do better anyway, as I was particularly quiet these 2 last months. So I use that time, where I’m waiting before driving to the airport to give a status.

I was quiet, but still working on it as time permitted, and willing to solve the Fedora 18-20 support issues I had for a very long time now. And it seems that with the latest patches pushed this week, I’m good on that side. I’ve been able to do a full backup/restore of my Fedora 20 VM in automatic mode without issue ! That’s the first time, and was particularly happy that after 9 months of development around 3.2, I could achieve that. The other good news, is that it is still working fine for RHEL 6 e.g. as I also did a full cycle this week.

Ok, so life is nice. Well, as you know, nothing’s perfect ;-) So I still have an issue with RHEL 7. In fully automatic mode, eveything works fine, except that the restored VM doesn’t start due to an issue on the UUID in the initramfs.

I’ll test by recreating that initramfs after restore, and hopfully, dracut will do the job for me. But as I’ll be travelling in the US all next week, I thought it was good to publish a last beta before leaving, so that the community could also test and report what happens on other distros or on other configurations.

Note that very few other bugs have been fixed. I’m more interested for this first 3.2 version to have it work finally on all new systemd distros as much as I can, even if some features are still not fully working (see trac for details).

Compared to my last post on the subject, some points have been improved:

  • the network stack is now launched as long as a network backup has been done originally, even if you boot from the ISO image directly, and not through PXE. You may still choose from where to restore afterwards, but at least network is up
  • solve some /bin vs /usr/bin issues for pre-fedora 18 and systemd distros which were not working anymore (Cf: #741)
  • fix for a lack of keyboard discovery
  • fix some perl issues in some cases (Cf: #755)
  • force LV creation which on RHEL7 now asks a question in case something was already there before (Cf: #753)
  • Optimize modules list computation between mindi and restore init script and do not load modules list twice anymore
  • Force generation of hardlinks for busybox to avoid package build problem on some distro with inexistant links at build time (recent SLES)
  • Fix busybox 1.21.1 to support back old distributions such as RHEL3 and RHEL4 or SLES9 by avoiding usage of the struct tpacket_auxdata
  • Fix isolinux.bin and ldlinux.c32 locations for recent Debian distro

So maybe even more has been fixed than I considered initially in fact. Anyway, I’ll try to avoid to stay so long without publishing new versions to test. It’s a promise, but will be difficult to keep so don’t hold your breath !

I’d appreciate that you provide feedback on the MondRescue mailing list, create trac entries (even if I know there are already a lot that would need to be solved sooner than later).

The goal is to publish 3.2.0 final before Christmas, and to work on a hopefully final 3.0.5 version backporting some of the previously mentionned fixes coded in 3.2 for those of you who prefer to stay on that branch, which will be maintained a bit in parallel as long as 3.2 is not tested more. I think that you’ve been patient with me, so I also have to be patient myself before more users adopt the new stable branch.

Hopefully you’ll get a new blog article for the announce in less than a month !

Some interesting stuff for MondoRescue 3.0.4

2013/06/25

Well at least I hope so !!

It took me much more time than I expected, and made me sleep at insane hours (yes really !), but I think that the beta that I built today under ftp://ftp.mondorescue.org/test/ should be of interest for MondoRescue users.

Some new distros are now added to the list of the one I’m building for (Ubuntu 13.04, Debian 7.1, Mageia 3, Fedora 18, …) Usual job for me, but hey, still of interest for people wanting the latest one.

Speaking of latest Debian, MondoRescue should now work better on it thanks to the fixes around #699 (NFS and SSHFS support), softlink in LocateDeps which have now their target scanned, and some deblint issues removed, including right test binaries placement, and man pages for perl scripts. I have someone working now with me on the re-integration of MondoRescue into Debian, so this version should help him reducing the diffs with his tree, and allow for the next steps (on the packaging itself) to go forward for our goal.

Of course, some annoying bugs reported have been fixed. At least we all hope so ;-)

  • grub2 support in #686 by adding grub.conf, grub.cfg and modified device.map.lst to device.map (Thanks to Victor Gattegno),
  • Fix support for OBDR tapes connected to SCSI cards and addition of an obdr modsboot parameter if some additional drivers should be removed,
  • an particularly nasty bug (there since rev 1 !) on SLES 11 SP2 by removing a dd in mindi which was filling the target dir,
  • the full management of scratch and tmp dir has been rewritten, hopefully for a better implementation now and a full resolution of #640,
  • the removal of the notion of number of media (limited to 50 abusively). Cf: #706
  • the addition of a -F option which allows mondoarchive to fail at first interaction. Cf: #702
  • sparse file support by adding a CLI parameter -M to modify the biggie file size limit, by default 64 MB, and by using st_blocks instead of st_size. Cf: #700
  • Fix #679 again and #685 by reducing the list of possible kernels (Thanks to Victor Gattegno and Didier Diaz)
  • Fix #696 for VGs not having a ‘-‘ in their name such as multipath aliases
  • Fix #703 by removing the errctl field used in star and log all star msgs into mondorestore.log. star is now considered production level as afio

And some improvements in the doc such as:

  • Adds more info in mindi log file (df -i, df -a, grub/lilo conf files, fdisk -l)
  • Add an example to use a fixed IP configuration at boot time through mindi.conf
  • Be more precise in messages displayed at restore time when a non-rewinding device should be used
  • Document the new -F and -M options
  • Precise the usage conditions of the exclude option (differences between device vs directory exclusion)
  • Indicate the other new tools than mkinitrd to help rebuilding the boot env (Thanks to Philippe Lefevre)
  • Precising compression rates on GUI button to ease choice (0 is no compression)

Some ongoing efforts at this point would require your help, dear reader to give appropriate feedback to see if we are making progresses:

  • Fix #628 by avoiding to erase choices done for variable bkpinfo->isodir and g_isodir_device in iso_fiddly_bits later in the code
  • Fix #208 by adding cifs support with first modifications to add cifs support as an external FS

So please help us by downloading this beta, which is IMO near from being the next stable and report wheher it’s working fine for you, or whether it’s working really fine for you ;-)

I have to say that most of these bugs wouldn’t have been fixed without the work I’ve done for HP’s customers recently, who are using extensively the tool, and were needing these fixes to have it fully working in their environment (RHEL and SLES in multiple versions on HP ProLiant servers). Pending their feedback on this version, I’ll declare it stable if they give me the green light, which should arrive soon now.

The PUSK 0.9.7 is now available

2013/05/17

What ? PUSK ? What’s that ? This is the ProLiant USB Setup Key :-)

This is a USB key you can now use to capture a hardware configuration of your HP ProLiant server (tested with G7 and Gen8). For that you just have to boot on the USB key and type “capture” at the boot prompt. Configuration is stored on the key, with the operation logs.

Then you can modify the conf files, or just use the single one we provide for what is really specific in a server (iLO credentials and IP conf), and redeploy that hardware configuration on a new server. For that just boot the new server on the key, and voilà !!

More over to deploy, you don’t need a keyboard, mouse, screen attached to the server, so if you are working in a place where your server is just electrically and networkly connected, that sufficient, and at the end the server will shutdown once the hardware configuration is done. Just restart it, and start controlling it remotely from the iLO do perform whatever further installation/customization you need to do.

So this is an easy way to have an operator perform the operation, doesn’t need Linux knowledge, nor platform knowledge. He just has to send the logs back to the dev team in case a problem occurs so they can debug.

And more over, thanks to HP, this is all GPLv2 Free Software ;-)

Now the important part, where to download it ?

The full 0.9.7 key is available at ftp://ftp.project-builder.org/PUSK/pusk-0.9.7.img
Just use dd to burn it onto your key and boot with it (WARNING: default mode is to deploy !)

For those of you who want to hack on the code, the entry point is at http://pusk.project-builder.org/browser/trunk and the Wiki (Home page) at http://pusk.project-builder.org

Hope you’ll find it useful. Let us know what you think of it.

Finally time to publish pb 0.12.2

2013/03/01

As you can see with the few messages I had time to post on this blog, the end of 2012 start of 2013 has been pretty busy, and I’m late in delivering the 2 projects I’m leading. So this week, I decided it was time to make a 0.12.2 version of pb, and make it available. Was asked by my colleagues of FOSSology, specially to add Fedora 18 support, so I also build my VMs to make packages on this distro.

BTW, a bit of ranting for Fedora once more: no perl by default :-(, and no ifconfig nor route command either which is breaking MondoRescue of course, and I guess tons of other software around. These guys don’t care about past, but don’t provide compatibility tools either !! So I’ll have to make new patches, just to do the same as what was done, but with another command again. Not to speak of systemd which I still have issues to deal with :-( That doesn’t make stuff go faster !

Anyway, the version is now out, no official bugs fixed, but a lot of small stuff here and there which were desrving a release. No time to test Fedora 17/18 VE yet, so you’ll have to do that yourself if you want. I also had a look at virsh usage in combination with pb, and it’s again not as easy as it could seem to be. Especially port redirection I’m easily using by launching qemu-kvm manually with the -redir or hostfwd option doesn’t seem to be possible with the user mode network through virsh (neither manager nor CLI). Will have to post on their ML to see how they do that, if they can !

And MondoRescue has been very late. I really need to publish a verion, but I still have some blocking bugs I really would like to get rid of: CTRL+ALT+DEL not working anymore during restore, some LVM issues on RHEL, some grub issues on SLES… Hopefully at the end of next week I’ll have made progresses.

Of course patches are much easy to integrate, but I receive more bug reports than them ;-)

And also back to preparing the HP internal TES event, Solutions Linux confs, submitting to LinuxCon, working on an FLOSS ITIL stack, learning more OpenStack, looking at Intel’s TXT…. so many things I’d like to do or learn and will never have time to ! Maybe at least I’ll talk about that another time.

Meet at HP Discover next week

2012/11/29

Hello,

I’ll be at the major HP event (HP Discover) next week in Frankfurt, Germany from the 4th to the 6th of December, delivering 2 sessions, and attenting some others which look very promising.

You may find me on the Red Hat booth or the Intel booth, if you want to talk about code and projects (MondoRescue, Project-Builder.org, UUWL), Architecture, FLOSS Governance, FLOSS @ HP or in general. Will be happy to exchange with you around these topics.

You may find more details (in french) on the sessions I’ll be delivering on the event blog site.

See you there !

MondoRescue 3.0.2 is now available

2012/06/05

I had to make this release in order to use it today (well yesterday now already !) on a customer site. That version was needed to support correctly software Raid on RHEL 6, with re-creation of metadata and UUIDs, which took a bit of time to make correctly. This version will also be welcome by Debian and Ubuntu users, as it fixes restoration issues, as well as on RHEL 5 (tune2fs command wasn’t working for ext4, and it required to use tune4fs, only available here !). It supports now out of tree kernel modules (such as hpsa from the PSP/SPP) and improve support for latest HP ProLiant Blades.

It fixes lots of small annoyances here and there (like #616), especially thanks to a test script that I have now developed to automate regression tests. This version was tested with it for rhel-6-x86_64, rhel-5-x86_64, debian-6.0-x86_64, ubuntu-11.04-i386, fully for the first time. I plan to extend it so that in the future I can cover more cases. And fixes also came from external contributors, which is very nice to see :-)

So, now time to rest a bit ! After project-builder.org and this version of MondoRecue, I can take a bit of time to think to the next steps, and more over, work on some other projects such as the UUWL and some I’ll announce later.

New Mondorescue 3.0.2 beta version available

2012/04/25

This version will fix again some problem met by customers or community users. Among these, as detailed earlier, the crash at restore time that was affecting users of MD software raid volumes, and the fact that we are now supporting UUID for their designation such as on RHEL 6.

Also for RHEL 5 users, there was an error on “no space left on device” at restore time, due to a modification in the way we are including more tools in the initrd, leading to the inclusion of the MAKEDEV program which was creating issue on device creation leading to that error message. It turns out this is also triggered by the busybox shell, so as we need anyway bash in the initrd, we will now use bash by default as the shell to launch all our scripts at restore time.

Mindi log files included in mondoarchive.log will also now be the expected one, not the one from an intermediate run.

2 contributors also provided fixes for issues: one for correct keyboard support by SLES by Victor Gattegno (who also helped around other bug fixes in this version), another one around the support of multiple PVs by bzium.

Even if 19 bugs were closed, I still have 2 issues that I’d like to fix before releasing 3.0.2: one around SLES grub install issue, and one around duplicate hpsa driver. And there are some others that may find their way in it. But that will be difficult, as I have a training in UK from the 2nd of May to the 4th of May, so I’ll publish the new version before in order to have it available at the training time !

So please test the beta version I made available at ftp://ftp.mondorescue.org/test and let me know if you find it stable for your case, and what other remaining issues you’d like me to work on next.

MondoRescue and Software Raid

2012/04/06

I had the opportunity to work for a customer whose infrastructure is using massively software RAID via md on a SAN storage. Their install base is made of RHEL6 VMs and they wanted to use MondoRescue for their imaging. What else as some could say ;-)

Recent versions of RHEL do use UUIDs everywhere, including to address MD devices in grub configuration, or mdadm ones. That doesn’t make the disaster recovery easier, if you recreate the device from scrtch with a new UUID. So the best approach is to store the information at backup and recreate them with the same UUID they had at restore time. But even if UUIDs on filesystems are supported since quite a long time now, it wasn’t the case for MD devices up to recent SVN revisions. In fact multiple issues were found, trying to make this support work correctly, which were gathered in some existing (and old) MondoRescue trac bugs (#73, #473, #500) or some especially raised at this occasion (#595 and #596).

I have now extended one of my test program to add MD tests as well, and it allowed me to finally solve all the remaining issues linked to this support. Hopefully ! In particular, we now also restore correctly the metadata format of the MD device, in order to be compliant with the boot loaders, as not all of them, or their versions, support all metadata versions. Not clear ? Well try to boot on a md device with the 1.2 version of metadata (created by default with latest mdadm create command) and you’ll rapidly understand ;-)

So as you could have guessed, the next step is now to produce a new set of packages in order for you to test ;-) As usual they will be available under ftp://ftp.mondorescue.org/test/ where you can pick probably your distribution of choice.

But that’s not all what I’d like to fix for the upcoming 3.0.2. I need to look closely at the bug #600 as we have an issue with the latest MondoRescue version on RHEL 5.x where x is recent as well. After I’ve fixed this one, I think we’ll be good to publish 3.0.2 officially, and start chasing other bugs for the next one ;-)


Follow

Get every new post delivered to your Inbox.

Join 123 other followers