Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l83yd-0005SP-2l for pgsql-bugs@arkaria.postgresql.org; Fri, 05 Feb 2021 16:28:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l83yb-0005uD-NU for pgsql-bugs@arkaria.postgresql.org; Fri, 05 Feb 2021 16:28:57 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l83ya-0005u5-Bp for pgsql-bugs@lists.postgresql.org; Fri, 05 Feb 2021 16:28:57 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l83yX-0008SP-HP for pgsql-bugs@lists.postgresql.org; Fri, 05 Feb 2021 16:28:55 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 40B015C00ED; Fri, 5 Feb 2021 11:28:52 -0500 (EST) Received: from imap21 ([10.202.2.71]) by compute2.internal (MEProxy); Fri, 05 Feb 2021 11:28:52 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eulerto.com; h= mime-version:message-id:in-reply-to:references:date:from:to:cc :subject:content-type; s=fm3; bh=Q1/VJOHCfY18QpxHNMa4OT0LIm1qNPr lQKrxlRxPy9M=; b=iaM5xiFXVKCXNKbqGgUD6u/uXEKeumBe6rwJ9vwqN33sRWS p097aUOroAegv9c08pOa1LzrZA237quzHOO52SBfqZtg5O+4uyxoYch3es4b2GiU L5deTP3WrJ/jrBu0CUkBLtLhfrKuZP9PnkSPEM5kalCTcGshREDHMQvTugREJCte 4MvrSCCubiqaWpvXZ1zMTrnguawb/DMtmk0LKsygQ5aC6l0mjGWvaFZGXHbKQN7Q yHlydHlUIOETZGJh94Os5X3QkjXV5KTuTGvsuhYK7n2JPWpgEWmgvNSId/PWGOtF O0HvMSk2w7qm83csOQvby3HISfBti6otV0Syt5g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=Q1/VJO HCfY18QpxHNMa4OT0LIm1qNPrlQKrxlRxPy9M=; b=byJ9RMobrqw8uBESldtYRv If9iAhuIWlcd2ZWiT2LakiLCnSzJNjB+6TfxXDGjG/dwvhVQ6/RRiHpqJmrb6ux7 YAecGPnA0eghQoVoTb7WZdnVsZmKs7VtKi+I5NjuHvX8U4cWPqWXbI0I9SraSi/N 6n++XdYBzHphwJuOUNU+TAhTzlzGtEqaxX/zF+TxaSgCgm/Psi2uSbjTOuIVJTtR uprn3CG2DISrT2Fb1EMPkxxfcL1HXG1vFlRwNzHAPSUqWLn1+0bQYZ58n6iv9ISe tm8a0vtJZOzTu+Uy410zuO0tqn5DEgpqEgi4YWzfYNTTYx0HR8iJXQLuygJNaVwA == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrgeeigdejvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsegrtderreerredtnecuhfhrohhmpedfgfhulhgv rhcuvfgrvhgvihhrrgdfuceovghulhgvrhesvghulhgvrhhtohdrtghomheqnecuggftrf grthhtvghrnhepudeuhedugeeffeeugfevvdeggeethfeffeeludeikeevtdetvddvfeef ueekgeevnecuffhomhgrihhnpehmihgtrhhoshhofhhtrdgtohhmpdgvnhhtvghrphhrih hsvggusgdrtghomhenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhl fhhrohhmpegvuhhlvghrsegvuhhlvghrthhordgtohhm X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id BBA2D51C0078; Fri, 5 Feb 2021 11:28:50 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-93-gef6c4048e6-fm-20210128.002-gef6c4048 Mime-Version: 1.0 Message-Id: <0d8da46b-e35b-45cc-a674-2a0678aa8bc6@www.fastmail.com> In-Reply-To: <106278.1612538775@sss.pgh.pa.us> References: <16854-905604506e23d5c0@postgresql.org> <59ad1f40-1bf2-a7e8-da22-7a279ea46efd@oss.nttdata.com> <106278.1612538775@sss.pgh.pa.us> Date: Fri, 05 Feb 2021 13:28:29 -0300 From: "Euler Taveira" To: "Tom Lane" , "Fujii Masao" Cc: katsuaki.fukushima@gmail.com, pgsql-bugs@lists.postgresql.org, peter.eisentraut@2ndquadrant.com Subject: Re: BUG #16854: initdb fails on ReFS and FAT32 file systems Content-Type: multipart/alternative; boundary=b85027ee093c4b6eab2619b6c70d980c List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --b85027ee093c4b6eab2619b6c70d980c Content-Type: text/plain On Fri, Feb 5, 2021, at 12:26 PM, Tom Lane wrote: > ReFS is Microsoft's latest and greatest attempt at implementing a modern > file system. I'd quantify the greatness pretty poorly if they left out > hard links (I wonder what other essentials they didn't bother with) > but maybe we have to support it. It claims that the latest ReFS version (3.5) supports hard links [1]. > On the third hand, Wikipedia says a bit further down > > The ability to create ReFS volumes was removed in Windows 10's 2017 > Fall Creators Update for all editions except Enterprise and Pro for > Workstations.[4] > > which sounds a whole lot like "we've already given up on this". > If they're not pushing ReFS anymore then I think we can ignore it. It is not clear why they removed the ability to create ReFS filesystems in some Windows 10 versions. Strategic decision? Even we fixed support for ReFS, they would be a mess to explain that a previous created ReFS filesystem doesn't support hard links and the OP should create a new one (unless MS provides a way to figure out that filesystem doesn't support hard links because it was created in a previous version). [1] https://docs.microsoft.com/en-us/windows-server/storage/refs/refs-overview -- Euler Taveira EDB https://www.enterprisedb.com/ --b85027ee093c4b6eab2619b6c70d980c Content-Type: text/html Content-Transfer-Encoding: quoted-printable
On Fri, Feb 5, = 2021, at 12:26 PM, Tom Lane wrote:
ReFS is Microsoft's latest and greatest attempt = at implementing a modern
file system.  I'd quantify t= he greatness pretty poorly if they left out
hard links (I = wonder what other essentials they didn't bother with)
but = maybe we have to support it.
It claims that t= he latest ReFS version (3.5) supports hard links [1].

=
On the third h= and, Wikipedia says a bit further down

&nbs= p;   The ability to create ReFS volumes was removed in Windows= 10's 2017
    Fall Creators Update for all= editions except Enterprise and Pro for
   = Workstations.[4]

which sounds a whole lot = like "we've already given up on this".
If they're not push= ing ReFS anymore then I think we can ignore it.
It is not clear why they removed the ability to create ReFS filesyste= ms in some
Windows 10 versions. Strategic decision? Even w= e fixed support for ReFS, they
would be a mess to explain = that a previous created ReFS filesystem doesn't
support ha= rd links and the OP should create a new one (unless MS provides a way
to figure out that filesystem doesn't support hard links bec= ause it was created
in a previous version).

=


--
Euler Taveira

--b85027ee093c4b6eab2619b6c70d980c--