NetWorker Blog

Commentary from a long term NetWorker consultant and Backup Theorist

  • This blog has moved!

    This blog has now moved to nsrd.info/blog. Please jump across to the new site for the latest articles (and all old archived articles).
  •  


     


     

  • Enterprise Systems Backup and Recovery

    If you find this blog interesting, and either have an interest in or work in data protection/backup and recovery environments, you should check out my book, Enterprise Systems Backup and Recovery: A Corporate Insurance Policy. Designed for system administrators and managers alike, it focuses on features, policies, procedures and the human element to ensuring that your company has a suitable and working backup system rather than just a bunch of copies made by unrelated software, hardware and processes.
  • This blog has moved!

    This blog has now moved to nsrd.info/blog. Please jump across to the new site for the latest articles (and all old archived articles).
  •  


     


     

  • Twitter

    Error: Twitter did not respond. Please wait a few minutes and refresh this page.

Aside – The scourge of filesystems

Posted by Preston on 2009-08-02

This morning I had to replace half of a mirror in my Linux server, which being a home server, meant needing to reboot. (Of course I’d love a server with hot-swappable drives, but I suspect both my partner and I might find the noise of such a server somewhat overwhelming for combination computer-room/office.)

So I shutdown the virtual machines running on the HP ML110 G4 (running VMware Server), shutdown the server itself, swapped the drives and rebooted. I promised my partner that internet access would only be down for about 15 minutes, so of course Murphy decided to play a visit.

“Warning, /dev/sdc1 has not been checked in 191 days. Check forced.”

And wouldn’t you know it, /dev/sdc1 is 917GB, so the check took quite a lot longer than 15 minutes. It’s running on ext3, so checking is required less frequently, but I’m still paranoid enough that for the data housed on that particular filesystem, I’d rather not turn checking off altogether. (That filesystem isn’t mirrored, due to transient data on it.)

Having only just read about btrfs, an upcoming filesystem for Linux, the lengthy delay-on-boot caused by a “large” filesystem check was acutely hammered home. Amongst other things, btrfs promises online checks of the filesystem, as well as fast offline checks of the filesystem – something every storage administrator and system administrator wants. We are at the point where filesystem capacities are routinely too large for conventional exhaustive checks. Many more modern filesystems have already achieved this (e.g., ZFS, VxFS, etc.), but it’s a relief to know that such advances are coming, and coming with corporate sponsorship, to Linux.

For an excellent overview of btrfs, check out this short history published on Linux Weekly News.

Advertisements

2 Responses to “Aside – The scourge of filesystems”

  1. David Magda said

    There’s a “basic” version of Veritas available:

    http://www.symantec.com/business/storage-foundation-basic

    Restrictions are:
    * Maximum four VxVM volumes per physical server (excluding system volumes required for booting root disks)
    * Maximum four mounted VxFS file systems per physical server (excluding root file systems)
    * Maximum physical server capacity of two CPU sockets

    http://eval.symantec.com/mktginfo/enterprise/other_resources/ent-sf_basic_5.0_technical_faq_01-2007.en-us.pdf

  2. Preston said

    David,

    Thanks for the reminder – I’d forgotten about the free/basic version of Foundation Suite.

    For small personal environments, it does have a nice fit.

    Cheers!

Sorry, the comment form is closed at this time.

 
%d bloggers like this: