Received: from trent.utfs.org (trent.utfs.org [94.185.90.103]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 6ECA7781A82 for ; Mon, 23 Dec 2019 03:23:08 +0000 (UTC) Received: from localhost (localhost [IPv6:::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by trent.utfs.org (Postfix) with ESMTPS id ED5825FE7B; Mon, 23 Dec 2019 04:23:06 +0100 (CET) Date: Sun, 22 Dec 2019 19:23:06 -0800 (PST) From: Christian Kujau To: Andrew Konstantinov cc: alpine-user@lists.alpinelinux.org Subject: Re: vfat mount uid/gid not working In-Reply-To: Message-ID: References: User-Agent: Alpine 2.21.99999 (DEB 375 2019-10-29) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII On Sun, 22 Dec 2019, Andrew Konstantinov wrote: > $ sudo mount -t /dev/sda1 /mnt/content -o rw,uid=1000,gid=1000 > $ sudo mount -v G content > /dev/sda1 on /mnt/content type vfat > (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=utf8,shortname=mixed,errors=remount-ro) Cannot reproduce on 5.4.5-0-virt (Alpine 3.12_alpha20191219), but something is curious about your mount commands: why specify "-t" but not fstype? What is "mount -v G..." supposed to do? Did you mean "... | grep conent"? ============================================================== $ mkfs.vfat /dev/loop0 $ mount -t vfat -o uid=1000,gid=1000 /dev/loop0 /mnt/ $ mount | grep /mnt /dev/loop0 on /mnt type vfat (rw,relatime,uid=1000,gid=1000,fmask=0066,dmask=0066,codepage=437,iocharset=utf8,shortname=mixed,errors=remount-ro) $ ls -ld /mnt/ drwx--x--x 2 dummy dummy 512 Dec 31 1969 /mnt/ ============================================================== Anything interesting in dmesg? Also, out of curiosity: why do you want to set uid/gid on a FAT filesystem? C. -- BOFH excuse #67: descramble code needed from software company