Uh Oh!! Made the contents of my directory unreadable
 

With this command or similar, I made my directory and one file in /
unreadable:

for entry in $(find $HOME); do $entry >> found; done

the same of output for ls is similar:

????????-k?x?B?{????U?I?3s??
???N???Q
?�w?Ϭw??9c̃}}Wz????Ǹ??t
Ç·~???
?^8?O?
?^???Â*?cB?f???????v????????V?!?@
???8%??????{??8?y??R??g??
??=c
?$??????�????????????~Ќ?t?)i}ˌW?6?
??:????G?x??g*D???S(?I%?=?m?ۼVݶT??ն)u??K[(????[??4?u???g?_??1M???QL?8*9?P
ã“‹?8M??4=?Î*?w3?m?'?Dv??u? ?s?Ƭ????A?q??a]??~:??????.Kd??ë—•oi?y????6:Ë¿???
N}Y?C????áº*?WÅ*?W???K0???vY? Z?1??
?U0?T*?A??̻?ɸ?ȶ?IJ???????????????????

Any ideas on how to fix this?

Uh Oh!! Made the contents of my directory unreadable
 

On Thursday 11 February 2010 19:58:25 ubiquitous1980 wrote:
> With this command or similar, I made my directory and one file in /
> unreadable:
>
> for entry in $(find $HOME); do $entry >> found; done
>
> the same of output for ls is similar:
>
> ????????-k?x?B?{????U?I?3s??
> ???N???Q
> ?�w?Ϭw??9c̃}}Wz????Ǹ??t
> Ç·~???
> ?^8?O?
> ?^???Â*?cB?f???????v????????V?!?@
> ???8%??????{??8?y??R??g??
> ??=c
> ?$??????�????????????~Ќ?t?)i}ˌW?6?
> ??:????G?x??g*D???S(?I%?=?m?ۼVݶT??ն)u??K[(????[??4?u???g?_??1M???QL?8*9?P
> ã“‹?8M??4=?Î*?w3?m?'?Dv??u? ?s?Ƭ????A?q??a]??~:??????.Kd??ë—•oi?y????6:Ë¿???
> N}Y?C????áº*?WÅ*?W???K0???vY? Z?1??
> ?U0?T*?A??̻?ɸ?ȶ?IJ???????????????????
>
> Any ideas on how to fix this?


Is the output given from the same shell session in which you ran the command?

Switch to a text console (Ctrl-Alt-Fx) and ls things there, perhaps the
garbage dumped to the screen in your for simply upset the terminal emulation.


--
alan dot mckinnon at gmail dot com

Uh Oh!! Made the contents of my directory unreadable
 

On Thu, 11 Feb 2010 20:18:29 +0200, Alan McKinnon wrote:

> Switch to a text console (Ctrl-Alt-Fx) and ls things there, perhaps the
> garbage dumped to the screen in your for simply upset the terminal
> emulation.

In which case, running reset in the affected terminal should clear it.


--
Neil Bothwick

Bookmark - A means of returning to where you got lost last time.

Uh Oh!! Made the contents of my directory unreadable
 

On Thursday 11 February 2010 18:18:29 Alan McKinnon wrote:

> perhaps the garbage dumped to the screen in your for simply upset the
> terminal emulation.

...in which case, perhaps typing RESET in the terminal will help.

--
Rgds
Peter.

Uh Oh!! Made the contents of my directory unreadable
 

On Thursday 11 February 2010 21:47:33 Neil Bothwick wrote:
> On Thu, 11 Feb 2010 20:18:29 +0200, Alan McKinnon wrote:
> > Switch to a text console (Ctrl-Alt-Fx) and ls things there, perhaps the
> > garbage dumped to the screen in your for simply upset the terminal
> > emulation.
>
> In which case, running reset in the affected terminal should clear it.

Every time I've tried to tell people to do that, they tell me they can't do it
because

%#!*^

obviously is not a valid command.

I've given up explaining :-)


--
alan dot mckinnon at gmail dot com

Uh Oh!! Made the contents of my directory unreadable
 

On Thu, 11 Feb 2010 22:32:44 +0200, Alan McKinnon wrote:

> > In which case, running reset in the affected terminal should clear
> > it.
>
> Every time I've tried to tell people to do that, they tell me they
> can't do it because
>
> %#!*^
>
> obviously is not a valid command.

It's not, if it were reset the second and fourth characters would be the
same :P

This tagline generator's at it again :)


--
Neil Bothwick

Light travels faster than sound. This is why some people appear bright
until you hear them speak.

Uh Oh!! Made the contents of my directory unreadable
 

On Friday 12 February 2010 00:26:56 Neil Bothwick wrote:
> On Thu, 11 Feb 2010 22:32:44 +0200, Alan McKinnon wrote:
> > > In which case, running reset in the affected terminal should clear
> > > it.
> >
> > Every time I've tried to tell people to do that, they tell me they
> > can't do it because
> >
> > %#!*^
> >
> > obviously is not a valid command.
>
> It's not, if it were reset the second and fourth characters would be the
> same :P

Smartass :-)

You owe me a year's subscription from your employer for that wise-crack.
Postage paid by sender, naturally.


--
alan dot mckinnon at gmail dot com

Uh Oh!! Made the contents of my directory unreadable
 

On Fri, 2010-02-12 at 01:58 +0800, ubiquitous1980 wrote:
> With this command or similar, I made my directory and one file in /
> unreadable:
>
> for entry in $(find $HOME); do $entry >> found; done

er... you just executed everything in your home directory and piped the
output to a file... I think you wanted "do echo $entry"? or the simpler
"find $HOME >> found"?

anyway, it shouldn't have corrupted your filesystem, but it looks like
it did.

> Any ideas on how to fix this?

you probably want to shutdown and fsck your filesystem. Then, start
looking for your backups :(

--
Iain Buchanan <iaindb at netspace dot net dot au>

Even with nougat you can have a perfect moment.
-- (Terry Pratchett, Thief of Time)

Uh Oh!! Made the contents of my directory unreadable
 

On Friday 12 February 2010 01:18:33 Iain Buchanan wrote:
> On Fri, 2010-02-12 at 01:58 +0800, ubiquitous1980 wrote:
> > With this command or similar, I made my directory and one file in /
> > unreadable:
> >
> > for entry in $(find $HOME); do $entry >> found; done
>
> er... you just executed everything in your home directory and piped the
> output to a file... I think you wanted "do echo $entry"? or the simpler
> "find $HOME >> found"?
>
> anyway, it shouldn't have corrupted your filesystem, but it looks like
> it did.

I thought the same and wondered "How? How could it corrupt stuff?"

So assuming the for did do the corruption and it isn't coincidence, what would
make this happen? Or is the OP just seriously out of luck and hit the one in a
gazillion unjackpot?

--
alan dot mckinnon at gmail dot com

Uh Oh!! Made the contents of my directory unreadable
 

Iain Buchanan wrote:
> On Fri, 2010-02-12 at 01:58 +0800, ubiquitous1980 wrote:
>
>> With this command or similar, I made my directory and one file in /
>> unreadable:
>>
>> for entry in $(find $HOME); do $entry >> found; done
>>
>
> er... you just executed everything in your home directory and piped the
> output to a file... I think you wanted "do echo $entry"? or the simpler
> "find $HOME >> found"?
>
> anyway, it shouldn't have corrupted your filesystem, but it looks like
> it did.
>
>
>> Any ideas on how to fix this?
>>
>
> you probably want to shutdown and fsck your filesystem. Then, start
> looking for your backups :(
>
>
Did just that. But no luck with fsck. So I had a tarballed and bzip2ed
backup from about a month ago and used that. Thanks for the suggestions
anyway guys :)