Hot from our test bench - kernel 4.5.0 still reports itself to be lustre 2.3.64 and still suffers this issue...
On Wed, Apr 20, 2016 at 5:19 PM, Dilger, Andreas <andreas.dil...@intel.com> wrote: > The version of Lustre in the upstream kernel for _features_ is pre-2.4, > but it has a large number of bug fixes since then. That means it can > connect to most normal Lustre servers, but does not have HSM or DNE or any > of the major features added in 2.4 and later. > > That is a restriction placed upon us in the kernel staging area until that > code is cleaned up sufficiently to be moved into the main tree. > > The master and 2.8 clients work up to at least kernel 4.2 and possibly > later, and are of course up-to-date feature wise. > > Cheers, Andreas > > On Apr 20, 2016, at 04:29, E.S. Rosenberg <esr+lus...@mail.hebrew.edu > <mailto:esr+lus...@mail.hebrew.edu>> wrote: > > So what version of lustre is built in to kernel 4.5? We are switching > distro soon at the very least to kernel 4.16 + userspace 2.7 and now would > definitely be the best time to still decide to use a newer kernel..... > > On Mon, Apr 18, 2016 at 10:28 PM, E.S. Rosenberg < > esr+lus...@mail.hebrew.edu<mailto:esr+lus...@mail.hebrew.edu>> wrote: > The servers are lustre 2.5.3 on CentOS 6.5 from the official RPMs > > The problem was tested on 2 clients, all running Debian with a kernel we > built. > - kernel 3.17.8, according to /proc/fs/lustre/version - 2.3.64, the > userspace programs (mount etc) are 2.5.3 > - kernel 4.1.6, /proc/fs/lustre/version - 2.3.64, userspace programs 2.7.52 > > Wow, that's really a mess when you try to use mainline kernel..... > > BTW according to LU-6232 it was not solved. > > Thanks, > Eli > > On Mon, Apr 18, 2016 at 10:12 PM, Dilger, Andreas < > andreas.dil...@intel.com<mailto:andreas.dil...@intel.com>> wrote: > What version of Lustre are you running? I thought we fixed that problem? > > Cheers, Andreas > > > On Apr 18, 2016, at 12:28, E.S. Rosenberg <esr+lus...@mail.hebrew.edu > <mailto:esr%2blus...@mail.hebrew.edu>> wrote: > > > > Hi all, > > Several of our users ran into the "Text file busy" error described in > LU-6232 (and possibly related to LU-4398 and LU-4429). > > > > Has there been any progress on this issue? > > > > I feel pretty dumb when I have to explain this issue to them and how to > work around it.... > > > > Thanks, > > Eli > > > > Background for those who don't like reading bug reports: > > When creating a script if it gets run subsequently it becomes impossible > to edit said script after it's been run even though it is not actively > running anymore. > > > > Workarounds I have seen so far: > > - Use an editor that moves the current file to a backup like emacs > (bypasses the issue since you are in practice working on a different file) > > - chmod -x the file before editing (reverts to being editable) > > - run the file using sh /path/to/file instead of /path/to/file (then it > stays editable) > > _______________________________________________ > > lustre-discuss mailing list > > lustre-discuss@lists.lustre.org<mailto:lustre-discuss@lists.lustre.org> > > http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org > > >
_______________________________________________ lustre-discuss mailing list lustre-discuss@lists.lustre.org http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org