Home > General Storage Devices, Linux, Red Hat, SSD, Storage, Ubuntu > Announcement: RapidDisk (rxdsk) 1.3b Stable release

Announcement: RapidDisk (rxdsk) 1.3b Stable release

November 23rd, 2011

I just released RapidDisk version 1.3b. The changelog documents the following changes:

  • Added new feature to archive/restore an rxd volume to/from a zlib compressed data file (many thanks to Simon Ball for suggesting a similar feature).
  • Added discard support.
  • Added an ioctl to handle an invalid query sent by later versions of udev that correspond with Linux kernels 2.6.35 and above.
  • Also integrated patch submitted by James Plummer of Stratus Technologies to address 32 bit limitation of rxadm utility rxdsk creation/resizing by casting the variable to a 64-bit type. Patch also included minor clean up code/optimizations for the same rxadm util.

Within the next week I will post a patch of 1.3 for the Linux 2.6.18 kernel.

Also, I postponed the integration of LZO compression/decompression into the kernel module until 1.4. I have still trying to get past a couple of hurdles for a stable implementation.

You can read more about this on the project’s wiki page. Also, just a reminder to all those interested, recently I created a Google+ page for the project, if you wish to stay posted on the latest news of this open source project.

  1. Simon Ball
    November 24th, 2011 at 03:06 | #1

    I’m very glad to see you are pursuing this project pkoutoupis. I look forward to testing this release next week when i have some more free time. I can at the moment test it under the following circumstances:

    - LAMP stack with multimedia deliverables
    - Virtualbox deployment

    I am currently away from a big rig but will be able to test it out using my netbook and would happily provide some feedback. I wonder if using such a resource constrained device will make a bigger difference.

    Again, thank you for your great work

  2. Simon Ball
    November 24th, 2011 at 05:45 | #2

    Another small suggestion for the project, to quote the man page a moment:

    rxadm returns a zero exit status if no error occurs during operation. A non- zero value is returned on error.

    Instead of returning a zero, might I suggest returning the location of the rxdsk device. This would allow piping for any further operations outside of the program scope. Admittedly, this entails checking that what gets returned isn’t an error through current modus operandi, but that’s not so much a problem.

    For the case where errors do occur, initial speculation presents two methods to make this work:

    - Return a 0 on failure. User can call “rxadm –errors” for feedback
    - Have an index of error codes:
    0 – success
    1 – Operation failed due to permissions
    2 – Operation failed due to insufficient space
    3 – Mounting archive failed due to read problems

    Just some food for thought. Kudos :)

  3. Simon Ball
    November 24th, 2011 at 05:47 | #3

    Apologies for spam with third post. With regards to error code index as described above.

    My reason for such a suggestion would be that a location will never be just an integer, so whether returning an error or location, it would be very simple to differentiate between the two

  4. pkoutoupis
    November 25th, 2011 at 14:22 | #4

    @Simon Ball

    Thank you very much for the suggestions. I will see what I can do with the features you are asking for.

    I do apologize for the late reply but regarding your comment on testing it on your netbook, I wanted to share with you that in my development of all releases, my netbook and also a VirtualBox guest on that same netbook were used. Although, nothing would compare to utilizing the power of a 64-bit server…

Comments are closed.