From: "Trever L. Adams" <tadams-lists@myrealbox.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: ext3 and filename globbing with ext3
Date: 04 Apr 2003 15:43:24 -0500 [thread overview]
Message-ID: <1049489004.1213.18.camel@aurora.localdomain> (raw)
Linux aurora.localdomain 2.4.20-2.48 #1 Thu Feb 13 11:52:40 EST 2003
i686 athlon i386 GNU/Linux
$ rpm -qa | grep openssh
openssh-askpass-gnome-3.5p1-6
openssh-3.5p1-6
openssh-server-3.5p1-6
openssh-askpass-3.5p1-6
openssh-clients-3.5p1-6
Okay, here we go. Earlier today, I erased several images from my local
working directory for a website. I updated several other things and
then ran the following:
scp -r pics user@site:/home/trever/somewebsite/
speachbubbleLONG.jpg 100% |*****************************| 2868
00:00
speachbubble.jpg 100% |*****************************| 3428
00:00
speechLONG-L.jpg 100% |*****************************| 2868
00:00
speechLONG-R.jpg 100% |*****************************| 2868
00:00
speech-L.jpg 100% |*****************************| 3428
00:00
speech-R.jpg 100% |*****************************| 3428
00:00
speechLONG-L.jpg 100% |*****************************| 4751
00:00
The speachbubble* were among the files I had erased about at least 15
minutes before hand (maybe over an hour).
This happened every time I used the command. However when I changed
into the pics directory and ran:
scp * user@site:/home/trever/somewebsite/pics/
It didn't copy those files, didn't even see them. An ls doesn't show
them either.
I have seen this happen several times before, I just realized for once
it is indeed a bug and not me messing up or imagining things.
My filesystem is mounted as ordered mode w/ ext3. Is this a known bug?
Trever Adams
--
One O.S. to rule them all, One O.S. to find them. One O.S. to bring them
all and in the darkness bind them.
reply other threads:[~2003-04-04 20:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1049489004.1213.18.camel@aurora.localdomain \
--to=tadams-lists@myrealbox.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®