From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: Hashim Aziz <hashaziz@hotmail.com>
Cc: cygwin <cygwin@cygwin.com>
Subject: Re: cat /proc/partitions shows only devices, not partitions
Date: Mon, 02 Mar 2020 16:56:00 -0000 [thread overview]
Message-ID: <20200302165634.GT4045@calimero.vinschen.de> (raw)
In-Reply-To: <DB7PR01MB51934E03BFDFE94142F1966FD5E60@DB7PR01MB5193.eurprd01.prod.exchangelabs.com>
[-- Attachment #1: Type: text/plain, Size: 2144 bytes --]
On Mar 1 21:16, Hashim Aziz wrote:
> This was an issue that I had previously in September of last year and
> sent the issue to this mailing list ("win-mounts no longer displays
> anything when doing "cat /proc/partitions") but the issue stopped
> occurring before I could get around to diagnosing it. This issue has
> now re-occurred and this time it seems permanent. When I run:
>
> $ cat /proc/partitions
> major minor #blocks name win-mounts
>
> 8 0 0 sda
> 8 16 0 sdb
> 8 32 0 sdc
> 8 48 0 sdd
> 8 64 0 sde
> 8 80 0 sdf
>
> ...I see nothing at all in the win-mounts column. This makes it
> impossible for me to see which Windows drive letter maps to which
> /dev/sdX entry. On closer inspection, this seems to be because I'm not
> actually seeing any partitions of my drives, even though there are
> many - for example, I see /dev/sda but no /dev/sda1 or /dev/sda2, and
> because it's the partitions that are mounted, it's this that seems to
> result in me seeing nothing in the win-mounts column. I'm running
> Cygwin on Windows 7 (yes I'm aware it's EOL).
Fortunately I just started Windows 7 for another thread here, so I
gave it a try myself:
$ uname -a
CYGWIN_NT-6.1 vmbert764 3.1.4(0.340/5/3) 2020-02-19 08:49 x86_64 Cygwin
$ id -G | grep -Eq '\<544\>' && echo elevated || echo non-elevated
non-elevated
$ cat /proc/partitions
major minor #blocks name win-mounts
8 0 54525952 sda
8 1 102400 sda1
8 2 54420480 sda2 C:\
So, https://cygwin.com/acronyms/#WJFFM
This appears to be a local phenomenon only, either some permission
problem, or some BLODA, a life virus scanner or something.
Two questions come to mind:
- Does it work in an elevated shell?
- If you run this under strace, does it show anything unusual?
We could take a look if you call
strace -o cat.trace cat /proc/partitions
and send the cat.trace file here (assuming it still doesn't work).
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-03-02 16:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-01 21:16 Hashim Aziz
2020-03-02 16:56 ` Corinna Vinschen [this message]
2020-03-04 19:35 ` Andrey Repin
2020-03-03 0:55 Hashim Aziz
2020-03-03 10:44 ` Corinna Vinschen
2020-03-03 1:01 Hashim Aziz
2020-03-03 17:21 Hashim Aziz
2020-03-03 18:17 ` Corinna Vinschen
2020-03-07 20:36 ` Hashim Aziz
2020-03-09 3:11 ` Andrey Repin
2020-03-09 15:47 Hashim Aziz
2020-03-09 15:59 ` Bill Stewart
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=20200302165634.GT4045@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
--cc=hashaziz@hotmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).