Sounds like one (or more) of your existing OSTs are out of space. The OSTs are assigned at file creation time, and Lustre will return an error if you cannot allocate space on the OST for a file you are writing. Do a "df" on your OSS nodes.
Lustre does not re-stripe files; you may have to manually move (cp/rm) some files to the new OST to rebalance the file system. It is a manual process, but you can use "lfs setstripe" for force a specific OST, and use "lfs getstripe" to see where a file's storage is allocated. Kevin Mag Gam wrote: > We have recently added another 1TB to a filesystem. We added a new OST > and mounted the OST. On the clients we do a lfs df -h and we see the > new space has been acquired. Also, lfs df -i shows enough inodes. > However, we randomly see 'No Space left on device (28)" when we run > our jobs. But if we resubmit the jobs it works again. > > Is there anything special we need to do, after we mount up a new OST? > > TIA > _______________________________________________ > Lustre-discuss mailing list > [email protected] > http://lists.lustre.org/mailman/listinfo/lustre-discuss > _______________________________________________ Lustre-discuss mailing list [email protected] http://lists.lustre.org/mailman/listinfo/lustre-discuss
