Menu
▾
▴
Re: [MooseFS-Users] Recent changes in MooseFS
|
From: Zlatko Č. <zca...@bi...> - 2017-02-09 14:35:24
|
That is great news, thanks for informing us! See a lot of fixes in there, so I might upgrade sooner rather than later, will report how it went. Keep up the good work! On 09.02.2017 15:12, Piotr Robert Konopelko wrote: > Dear MooseFS Users, > > We are proud to annonce, that *MooseFS 3.0.88* has been released > <https://github.com/moosefs/moosefs/releases/tag/v3.0.88> as stable today! > This version includes bugfixes and improves stability (mainly > concerning MooseFS Client). > > If you like MooseFS, please support it by starring it on GitHub > <https://github.com/moosefs/moosefs>. Opening an issue on GitHub > <https://github.com/moosefs/moosefs/issues> is also appreciated. Thanks! > > > Please find the changes in MooseFS 3 since 3.0.86 below: > > * *MooseFS 3.0.88-1 (2017-02-08)* > o (mount) added read cache clean on write (same file access > using different descriptors) > o (mount) added missing cond_destroy in readdata.c (fix sent by > Jakub Ratajczak) > o (master) fixed initializing packet size for reading > 'sustained' directory > o (all) fixed zassert for printing correct statuses in case of > pthread functions > > * *MooseFS 3.0.87-1 (2017-02-01)* > o (mount) fix fleng in finfo after truncate (patched by Davies Liu) > o (mount) fix overlapped read (patched by Davies Liu) > o (mount) fixed invalidating chunk cache after truncate > o (mount) fixed fleng handling in read worker > o (mount) fixed handling BREAK state in read worker > o (mount) changed handling data invalidation in read module > (sometimes could be less efficient, but it is much more safer) > o (tools) fixed number parsing (patched by Pawel Gawronski) > o (cli) fixed printed host/port options > o (mount) moved pipes from requests to workers (read and write - > huge decrease of descriptors used by mount) > o (mount) changed signal to broadcast in rwlock (fixed very rare > read/write deadlock) > o (mount) fixed 'open descriptors' leak (lookup(with data for > open)->open(with cached data)->close) > o (mount) fixed potential 'race condition' - free csdata during > access > o (master) split (only internally) sustained folder into 256 > subfolders (too many sustained files caused socket timeouts in > master) > > > > Best regards, > Peter / MooseFS Team > > -- > Piotr Robert Konopelko > *MooseFS Technical Support Engineer* | moosefs.com <https://moosefs.com> > >> On 02 Dec 2016, at 7:54 PM, Piotr Robert Konopelko >> <pio...@mo... <mailto:pio...@mo...>> wrote: >> >> Dear MooseFS Users, >> >> we released the newest version MooseFS 3.0 recently: MooseFS 3.0.86. >> This version mainly contains bugfixes and improves stability. >> >> >> *We strongly recommend to upgrade to the latest version,* but please >> remember, that If you had version lower than 3.0.83 and then you >> upgraded your Chunkservers to v. 3.0.83 or higher, *please DO NOT >> downgrade them!* >> *In MooseFS Chunkserver v. 3.0.83 we changed Chunk header from 5k to >> 8k (see changelog) - this is one of major changes and it means, that >> Chunkserver older than 3.0.83 cannot "understand" new Chunk header, >> which may lead to potential data loss!* >> >> >> If you like MooseFS, please support it by starring it on GitHub >> <https://github.com/moosefs/moosefs>. Thanks! >> >> >> Please find the changes in MooseFS 3 since 3.0.77 below: >> >> * *MooseFS 3.0.86-1 (2016-11-30)* >> o (master) fixed leader-follower resynchronization after >> reconnection (pro only) >> o (master) fixed rehashing condition in edge/node/chunk >> hashmaps (change inspired by yinjiawind) >> >> * *MooseFS 3.0.85-1 (2016-11-17)* >> o (mount) fixed memory leak (also efficiency) on Linux and >> potential segfaults on FreeBSD (negative condition) >> o (mount) fixed race condition for inode value in write module >> o (mount) better descriptors handling (lists of free elements) >> o (mount) better releasing descriptors on FreeBSD >> o (cs) fixed time condition (patch send by yinjiawind) >> >> * *MooseFS 3.0.84-1 (2016-10-06)* >> o (master) fixed setting acl-default without named users or >> named groups >> o (master) fixed master-follower synchronization after setting >> storage class >> >> * *MooseFS 3.0.83-1 (2016-09-30)* >> o *(cs) changed header size from 5k to 8k (due to 4k-sector >> hard disks)* >> >> * *MooseFS 3.0.82-1 (2016-09-28)* >> o (all) silenced message about using deprecated parameter 'oom_adj' >> o (mount) fixed FreeBSD delayed release mechanism >> o (mount) added rwlock for chunks >> >> * *MooseFS 3.0.81-1 (2016-07-25)* >> o (mount) fixed oom killer disabling (setting oom_adj and >> oom_score_adj) >> o (cli) fixed displaying inactive mounts >> o (mount) added fsync before removing any locks >> o (daemons) added disabling oom killer (Linux only) >> o (all) small fixes in manpages >> o (mount) fixed handling nonblocking lock commands (unlock and >> try) in both locking mechanisms >> o (daemons+mount) changed default settings for limiting malloc >> arenas (Linux only) >> >> * *MooseFS 3.0.80-1 (2016-07-13)* >> o (master) fixed chunk loop (in some cases chunks from the last >> hash position might be left unchecked) >> o (master) fixed storage class management (fixed has_***_labels >> fields) >> >> * *MooseFS 3.0.79-1 (2016-07-05)* >> o (master) fixed 'flock' (change type of lock SH->EX and EX->SH >> caused access to freed memory and usually SEGV) >> >> * *MooseFS 3.0.78-1 (2016-06-14)* >> o *(cs) fixed serious error that may cause data corruption >> during internal rebalance (intr. in 3.0.75)* >> >> >> >> >> Best regards, >> Peter >> >> -- >> >> MooseFS <https://moosefs.com/> >> >> Piotr Robert Konopelko >> MooseFS Technical Support Engineer >> e-mail: pio...@mo... <mailto:pio...@mo...> >> www: https://moosefs.com <https://moosefs.com/> >> >> Twitter <https://twitter.com/MooseFS>Facebook >> <https://www.facebook.com/moosefs>LinkedIn >> <https://www.linkedin.com/company/moosefs>GitHub >> <https://github.com/moosefs> >> >> This email and any files transmitted with it are confidential and >> intended solely for the use of the individual or entity to whom they >> are addressed. If you have received it by mistake, please let us know >> by e-mail reply and delete it from your system; you may not copy this >> message or disclose its contents to anyone. Finally, the recipient >> should check this email and any attachments for the presence of >> viruses. Core Technology accepts no liability for any damage caused >> by any virus transmitted by this email. >> >> >>> On 08 Jun 2016, at 1:04 AM, Piotr Robert Konopelko >>> <pio...@mo... <mailto:pio...@mo...>> >>> wrote: >>> >>> Dear MooseFS Users, >>> >>> we released the newest versions of both MooseFS 3.0 and MooseFS 2.0 >>> recently: 3.0.77 and 2.0.89. >>> >>> They improve MooseFS stability and (in MooseFS 3.0) also add new >>> features, like: >>> >>> * Storage Classes <https://moosefs.com/documentation/moosefs-3-0.html> >>> * Possibility to mount MooseFS on Linux by issuing: *mount -t >>> moosefs mfsmaster.example.lan: /mnt/mfs* >>> * File sparsification >>> * Automatic temporary maintenance mode >>> * New I/O synchronisation between different mounts >>> >>> If you like MooseFS, please support it by starring it on GitHub >>> <https://github.com/moosefs/moosefs>. Thanks! >>> >>> >>> Please find the changes in MooseFS 3 since 3.0.73 below: >>> >>> * *MooseFS 3.0.77-1 (2016-06-07)* >>> o (mount) added assertions after packet allocation in master >>> communication module >>> o (manpages) fixes related to storage classes >>> o (all) improved error messages used for storage classes >>> >>> * *MooseFS 3.0.76-1 (2016-06-03)* >>> o (master) fixed resolving multi path for root inode >>> o (master) fixed licence expiration behaviour (pro only) >>> >>> * *MooseFS 3.0.75-1 (2016-04-20)* >>> o (all) fixed cppcheck warnings/errors (mostly false negatives) >>> o (cs) added file sparsification during chunk write (also >>> chunk replication, chunk duplication etc.) >>> o (mount) fixed write data inefficiency when I/O was performed >>> by root >>> o (master) fixed removing too early locked chunks from data >>> structures >>> o (tools) fixed reusing local ports (connection to master >>> returned EADDRNOTAVAIL) >>> o (all) changed default action from restart to start >>> o (all) added exiting when user defined config (option -c) >>> cannot be loaded >>> o (cs) changed handling chunk filename (dynamic filename >>> generation - cs should use less memory) >>> o (netdump) changed 'moose ports only' option to 'port range' >>> o (mount) limited number of files kept as open after close >>> o (cs) changed subfolder choosing algorithm >>> o (mount) changed mutex lock to rw-lock for I/O on the same >>> descriptor >>> o (mount) added link to mfsmount from '/sbin/mount.moosefs' >>> (Linux only) >>> o (all) introduced "storage classes" (new goal/labels management) >>> o (master+cs) introduced 'temporary maintenance mode' >>> (automatic maintenance mode after graceful stop of cs) >>> o (master+mount) added fix for bug in FreeBSD kernel (kernel >>> sends truncate before first close - FreeBSD only) >>> o (cs) fixed setting malloc pools on Linux >>> >>> * *MooseFS 3.0.74-1 (2016-03-08)* >>> o (master) fixed rebalance replication (check for all chunk >>> copies for destination - not only valid) >>> o (master+mount) new mechanism for atime+mtime setting during I/O >>> o (master+mount) new I/O synchronization between different >>> mounts (with cache invalidation) >>> o (master+mount) new chunk number/version cache (with >>> automatic invalidation from master) >>> o (master) added mapping chunkserver IP classes (allow to have >>> separate network for I/O and separate for other activity) >>> o (master) fixed status returned by writechunk after network >>> down/up >>> o (master) changed trashtime from seconds to hours >>> o (master) added METADATA_SAVE_FREQ option (allow to save >>> metadata less frequently than every hour) >>> o (master) added using in emergency (endangered chunks) all >>> available servers for replication (even overloaded and being >>> maintained) >>> o (master) added using chunkservers in 'internal rebalance' >>> state in case of deleting chunks >>> o (all) spell check errors fixed (patch contributed by Dmitry >>> Smirnov) >>> >>> >>> Please find the changes in MooseFS 2.0 since 2.0.88 below: >>> >>> * *MooseFS 2.0.89-1 (2016-04-27)* >>> o (master+mount) added fix for bug in FreeBSD kernel (kernel >>> sends truncate before first close - FreeBSD only) >>> >>> >>> Best regards, >>> >>> >>> -- >>> >>> <Mail Attachment.png> <https://moosefs.com/> >>> >>> Piotr Robert Konopelko >>> MooseFS Technical Support Engineer >>> e-mail: pio...@mo... <mailto:pio...@mo...> >>> www: https://moosefs.com <https://moosefs.com/> >>> >>> <Mail Attachment.png> <https://twitter.com/MooseFS> <Mail >>> Attachment.png> <https://www.facebook.com/moosefs> <Mail >>> Attachment.png> <https://www.linkedin.com/company/moosefs> <Mail >>> Attachment.png> <https://github.com/moosefs> >>> >>> This email and any files transmitted with it are confidential and >>> intended solely for the use of the individual or entity to whom they >>> are addressed. If you have received it by mistake, please let us >>> know by e-mail reply and delete it from your system; you may not >>> copy this message or disclose its contents to anyone. Finally, the >>> recipient should check this email and any attachments for the >>> presence of viruses. Core Technology accepts no liability for any >>> damage caused by any virus transmitted by this email. >>> >>> >>>> On 08 Mar 2016, at 9:24 AM, Piotr Robert Konopelko >>>> <pio...@mo... <mailto:pio...@mo...>> >>>> wrote: >>>> >>>> Dear MooseFS Users, >>>> >>>> we released the newest versions of both MooseFS 3 and MooseFS 2 >>>> recently: 3.0.73 and 2.0.88. >>>> >>>> Please find the changes in MooseFS 3 since 3.0.71 below: >>>> >>>> * *MooseFS 3.0.73-1 (2016-02-11)* >>>> o (master) fixed restoring ARCHCHG from changelog >>>> o (cli+cgi) fixed displaying master list with followers only >>>> (pro version only) >>>> o (master) added using size and length quota to fix disk >>>> usage values (statfs) >>>> o (master) fixed xattr bug which may lead to data corruption >>>> and segfaults (intr. in 2.1.1) >>>> o (master) added 'node_info' packet >>>> o (tools) added '-p' option to 'mfsdirinfo' - 'precise mode' >>>> o (master) fixed edge renumeration >>>> o (master) added detecting of wrong edge numbers and force >>>> renumeration in such case >>>> >>>> * *MooseFS 3.0.72-1 (2016-02-04)* >>>> o (master+cgi+cli) added global 'umask' option to exports.cfg >>>> o (all) changed address of FSF in GPL licence text >>>> o (debian) removed obsolete conffiles >>>> o (debian) fixed copyright file >>>> o (mount) fixed parsing mfsmount.cfg (system options like >>>> nodev,noexec etc. were ommited) >>>> o (master) changed way how cs internal rebalance state is >>>> treated by master (as 'grace' state instead of 'overloaded') >>>> o (mount) fixed bug in read module (setting etab after ranges >>>> realloc) >>>> o (tools) removed obsoleted command 'mfssnapshot' >>>> >>>> >>>> >>>> Please find the changes in MooseFS 2 since 2.0.83 below: >>>> >>>> * *MooseFS 2.0.88-1 (2016-03-02)* >>>> o (master) added METADATA_SAVE_FREQ option (allow to save >>>> metadata less frequently than every hour) >>>> >>>> * *MooseFS 2.0.87-1 (2016-02-23)* >>>> o (master) fixed status returned by writechunk after network >>>> down/up >>>> >>>> * *MooseFS 2.0.86-1 (2016-02-22)* >>>> o (master) fixed initialization of ATIME_MODE >>>> >>>> * *MooseFS 2.0.85-1 (2016-02-11)* >>>> o (master) added ATIME_MODE option to set atime modification >>>> behaviour >>>> o (master) added using size and length quota to fix disk >>>> usage values (statfs) >>>> o (all) changed address of FSF in GPL licence text >>>> o (debian) removed obsolete conffiles >>>> o (debian) fixed copyright file >>>> o (mount) fixed parsing mfsmount.cfg (system options like >>>> nodev,noexec etc. were ommited) >>>> o (tools) removed obsoleted command 'mfssnapshot' >>>> >>>> * *MooseFS 2.0.84-1 (2016-01-19)* >>>> o (mount) fixed setting file length in write module during >>>> truncate (fixes "git svn" case) >>>> >>>> >>>> Best regards, >>>> >>>> -- >>>> >>>> <Mail Attachment.png> <https://moosefs.com/> >>>> >>>> Piotr Robert Konopelko >>>> MooseFS Technical Support Engineer >>>> e-mail: pio...@mo... >>>> <mailto:pio...@mo...> >>>> www: https://moosefs.com <https://moosefs.com/> >>>> >>>> <Mail Attachment.png> <https://twitter.com/MooseFS> <Mail >>>> Attachment.png> <https://www.facebook.com/moosefs> <Mail >>>> Attachment.png> <https://www.linkedin.com/company/moosefs> <Mail >>>> Attachment.png> <https://github.com/moosefs> >>>> >>>> This email and any files transmitted with it are confidential and >>>> intended solely for the use of the individual or entity to whom >>>> they are addressed. If you have received it by mistake, please let >>>> us know by e-mail reply and delete it from your system; you may not >>>> copy this message or disclose its contents to anyone. Finally, the >>>> recipient should check this email and any attachments for the >>>> presence of viruses. Core Technology accepts no liability for any >>>> damage caused by any virus transmitted by this email. >>>> >>>> >>>>> On 27 Jan 2016, at 5:51 PM, Piotr Robert Konopelko >>>>> <pio...@mo... <mailto:pio...@mo...>> >>>>> wrote: >>>>> >>>>> Dear MooseFS Users, >>>>> >>>>> today we published the newest version from 3.x branch: 3.0.71. >>>>> >>>>> Please find the changes since 3.0.69 below: >>>>> >>>>> * *MooseFS 3.0.71-1 (2016-01-21)* >>>>> o (master) fixed emptying trash issue (intr. in 3.0.64) >>>>> o (master) fixed possible segfault in chunkservers database >>>>> (intr. in 3.0.67) >>>>> o (master) changed trash part choice from nondeterministic >>>>> to deterministic >>>>> >>>>> * *MooseFS 3.0.70-1 (2016-01-19)* >>>>> o (cgi+cli) fixed displaying info when there are no active >>>>> masters (intr. in 3.0.67) >>>>> o (mount+common) refactoring code to be Windows ready >>>>> o (mount) added option 'mfsflattrash' (makes trash look like >>>>> before version 3.0.64) >>>>> o (mount) added fixes for NetBSD (patch contributed by Tom >>>>> Ivar Helbekkmo) >>>>> >>>>> >>>>> Best regards, >>>>> >>>>> -- >>>>> Piotr Robert Konopelko >>>>> *MooseFS Technical Support Engineer*| moosefs.com >>>>> <https://moosefs.com/> >>>>> >>>> >>>> >>> >>> >> > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > > > _________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users -- Zlatko |
