linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <yuchao0@huawei.com>
To: Patrick Doyle <wpdster@gmail.com>,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: Are there limitation to the number of named pipes/FIFO's supported by F2FS?
Date: Wed, 5 Sep 2018 09:55:28 +0800	[thread overview]
Message-ID: <a24181da-6e5f-63de-d2fa-7c14c8ed592f@huawei.com> (raw)
In-Reply-To: <CAF_dkJChk25fWa+bTndWa-qRsy6mW3Mj3uemXpk0QxLgY=fzeg@mail.gmail.com>

On 2018/9/5 0:28, Patrick Doyle wrote:
> I have created an f2fs partition on which to build embedded Linux
> images (using Yocto/OpenEmbedded/Bitbake).
> 
> I just had a build fail where all 20 parallel makes failed with errors
> of the form:
> 
> OSError: [Errno 5] Input/output error:
> '/home/wpd/src/20180904-test/apps_proc/poky/build/tmp-glibc/work/armv7a-vfp-neon-oe-linux-gnueabi/libxml2/2.9.2-r0/temp/fifo.32426'

I don't remember there is any restriction to create named pipes/FIFO. If you can
provider more info about the building failure, maybe I can help to trouble shoot
the issue.

Is there no more free inode space? can you show me filesystem usage by 'stat -f'?

> 
> This build completed successfully in the past, including just this
> morning (on this filesystem).
> 
> I believe by design (and benchmarks I have researched) that F2FS is
> the best approach for SSD based file systems, but this will mark the
> second time in less than a week of having put F2FS in operation that I
> will have to back up my partition, reformat it with different flags,
> and restore it from my backup.   I am now frustrated.
> 
> What options would you recommend for a 1TB SSD formatted with F2FS to
> be used in an environment that generates Linux system images?  This
> environment creates many object files, named pipes, logfiles, etc...
> 
> I will start my new backup now, and hope to learn your recommendation
> before I am ready to issue my next mkfs command.

Do you upgrade both mkfs and kernel? and use mkfs -i to format your ssd device?

Thanks,

> 
> --wpd
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
> 
> 


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

  reply	other threads:[~2018-09-05  1:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-04 16:28 Are there limitation to the number of named pipes/FIFO's supported by F2FS? Patrick Doyle
2018-09-05  1:55 ` Chao Yu [this message]
2018-09-05  4:12   ` Jaegeuk Kim
2018-09-05 13:35     ` Patrick Doyle
2018-09-05 15:57       ` Chao Yu
2018-09-05 16:11         ` Patrick Doyle
2018-09-05 17:30           ` Jaegeuk Kim
2018-09-06  1:51           ` Chao Yu
2018-09-06 13:14             ` Patrick Doyle
2018-09-06 13:29               ` Chao Yu
2018-09-06  2:03           ` Chao Yu
2018-09-06 12:44             ` Chao Yu
2018-09-06 13:31             ` Patrick Doyle
2018-09-05 17:16         ` Jaegeuk Kim

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a24181da-6e5f-63de-d2fa-7c14c8ed592f@huawei.com \
    --to=yuchao0@huawei.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=wpdster@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).