From: Neeraj Singh <nksingh85@gmail.com>
To: Attila Csosz <csosza@designsoftware.com>,
"brian m. carlson" <sandals@crustytoothpaste.net>,
git@vger.kernel.org
Subject: Re: Git bug report - disk errors on Windows after push
Date: Wed, 20 Apr 2022 15:54:24 -0700 [thread overview]
Message-ID: <04a50f96-363f-210f-b894-11945d0eb3e8@gmail.com> (raw)
In-Reply-To: <fa40a6e6-dd83-9e88-e2f7-ab8aff2ca5a4@designsoftware.com>
On 4/18/2022 8:52 PM, Attila Csosz wrote:
> I've experienced the problem at least 3 different external disk.
> I'm not using cloud syncing service (e.g., Dropbox or OneDrive) for git.
>
> Attila
>
Hi Attila,
Could you please share a bit more information about the disks that are
being corrupted and the specific error messages you're seeing?
What is the underlying storage type (e.g. USB key, external hard drive,
etc)? Also, which filesystem is the drive formatted as?
Could you please save one instance of a volume in the corrupted state so
that we can consider further investigations?
I believe the output of "fsutil fsinfo volumeinfo <drive letter>" and
"fsutil fsinfo drivetype <drive letter>" should give us some useful info
about the volume that's being corrupted.
Thanks,
Neeraj Singh,
Windows FileSystem Dev
next prev parent reply other threads:[~2022-04-20 22:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 7:47 Git bug report - disk errors on Windows after push Attila Csosz
2022-04-18 17:37 ` brian m. carlson
2022-04-19 3:52 ` Attila Csosz
2022-04-20 21:28 ` brian m. carlson
2022-04-20 22:54 ` Neeraj Singh [this message]
2022-04-21 2:29 ` Attila Csosz
2022-04-21 20:08 ` Neeraj Singh
2022-04-22 9:27 ` Ævar Arnfjörð Bjarmason
2022-04-22 15:04 ` Attila Csosz
2022-04-22 16:13 ` Junio C Hamano
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=04a50f96-363f-210f-b894-11945d0eb3e8@gmail.com \
--to=nksingh85@gmail.com \
--cc=csosza@designsoftware.com \
--cc=git@vger.kernel.org \
--cc=neerajsi@microsoft.com \
--cc=sandals@crustytoothpaste.net \
/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).