ru.unix.bsd

 
 - RU.UNIX.BSD ------------------------------------------------------------------
 From : Slawa Olhovchenkov                   2:5030/500     09 Mar 2007  14:13:54
 To : All
 Subject : Вести с полей
 -------------------------------------------------------------------------------- 
 

 
 From: Ivan Voras <ivoras@fer.hr>
 Subject: First steps towards importing gvirstor into -current
 
 Hi!
 
 As announced, the plan was to start working on importing gvirstor into
 CVS after 6.2 was successfully released. For those who don't know,
 gvirstor is a GEOM class providing storage virtualisation facility, i.e.
 its purpose is to offer the ability to create a virtual storage device
 of arbitrarily large size (typically several terabytes) which consists
 of an arbitrary number of physical storage devices (actually any
 lower-level GEOM providers, including RAID devices) of arbitrary size
 (typically 50 GB - 400 GB hard drives).
 
 The latest sources are available in p4 and conveniently on FreeBSD's
 wiki site: http://wiki.freebsd.org/gvirstor .
 
 There are some known minor issues that will be fixed in the following
 days (mostly related to overly verbose error messages), so (at the
 suggestion of my mentor - pjd) I'm inviting interested users to try it
 out and report any problems found (if there are such). Also, benchmarks
 of gvirstor in close-to-real-life usage are welcome.
 
 The idea is to stabilize the current code, and new features will be
 developed later.
 
 ====
 
 Features
 
 Here is a short list of features gvirstor provides:
 
     * Creates storage devices in "overcommit" mode, larger than physically
 available storage
     * Can create devices of arbitrary size, upto 2^63 bytes, with arbitrary
 chunk (extent) size
     * Notifies via kernel-syslog mechanism when used-up storage approaches
 available storage (watermark values for these warnings are controllable with
 sysctls)
     * Allows adding new storage devices (components) at runtime, when virstor
 device is "hot"
     * Allows removing storage devices (components) when they are unused and at
 the end of list of added components
     * Updates virstor allocation table (i.e. metadata) synchronously with write 
 requests (all considerations with drive caches still remain, but if the drive
 doesn't lie, the data is safe)
 ... Даже маленькая практика стоит большой теории
 --- GoldED+/BSD 1.1.5
  * Origin:  (2:5030/500)
 
 

Вернуться к списку тем, сортированных по: возрастание даты  уменьшение даты  тема  автор