From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick Doyle Subject: Re: Are there limitation to the number of named pipes/FIFO's supported by F2FS? Date: Wed, 5 Sep 2018 09:35:27 -0400 Message-ID: References: <20180905041210.GB15147@jaegeuk-macbookpro.roam.corp.google.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from [172.30.20.202] (helo=mx.sourceforge.net) by sfs-ml-1.v29.lw.sourceforge.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) (envelope-from ) id 1fxXyV-0000lm-DF for linux-f2fs-devel@lists.sourceforge.net; Wed, 05 Sep 2018 13:36:03 +0000 Received: from mail-oi0-f65.google.com ([209.85.218.65]) by sfi-mx-2.v28.lw.sourceforge.com with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.90_1) id 1fxXyR-001nin-Sz for linux-f2fs-devel@lists.sourceforge.net; Wed, 05 Sep 2018 13:36:03 +0000 Received: by mail-oi0-f65.google.com with SMTP id y207-v6so13542963oie.13 for ; Wed, 05 Sep 2018 06:35:59 -0700 (PDT) In-Reply-To: <20180905041210.GB15147@jaegeuk-macbookpro.roam.corp.google.com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: linux-f2fs-devel-bounces@lists.sourceforge.net To: jaegeuk@kernel.org Cc: linux-f2fs-devel@lists.sourceforge.net On Wed, Sep 5, 2018 at 12:12 AM Jaegeuk Kim wrote: > On 09/05, Chao Yu wrote: > > 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'? > > Me too. I don't think F2FS does something on pipes. :P Thank you both for your replies. As per our previous email exchange, I had formatted the filesystem with the "-i" option. There were plenty of free inodes. I don't know what could have led to this issue. This is a production system for me, so I can't afford to spend any more time trying to debug this. I have made 2 changes to my production system in the past 10 days: I installed a 1TB SSD, and I formatted it with F2FS. I have run into show-stopping problems twice with this new configuration. In the first case, I learned about the "-i" option, and I saw that help (after I backed up all of my data and reformatted). In the second case, I ran into that bizarre build failure. It is possible that the root cause of that failure is bad hardware (the new SSD). It is possible that there is a latent bug in the F2FS implementation that is exposed under heavy load on my 24-core Xeon system. It is possible that the second problem was a random occurrence and I would never see it again. Regardless, I can't afford to lose another day tracking this down. I have reformatted the SSD with an ext4 FS and I am crossing my fingers that the hardware is not the root cause. For your own reference, I am running my production system on Ubuntu 16.04 LTS with a "4.15.0-33-generic" kernel. --wpd ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot