Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Sat 18 Nov 2017, 00:53
All times are UTC - 4
 Forum index » House Training » Beginners Help ( Start Here)
mv and cp commands not working correctly
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 1 [10 Posts]  
Author Message
bostonvaulter


Joined: 26 Sep 2006
Posts: 269

PostPosted: Thu 05 Oct 2006, 14:23    Post subject:  mv and cp commands not working correctly  

recently i have been having a strange bug where mv won't work correctly. I'll try to move a file. everything seems like it's working okay. but then when i do ls, it's still in the same directory! does anyone have any hints or suggestions?
Last edited by bostonvaulter on Thu 05 Oct 2006, 16:23; edited 1 time in total
Back to top
View user's profile Send private message 
Braden

Joined: 22 Sep 2006
Posts: 70
Location: Waterloo, Ontario, Canada

PostPosted: Thu 05 Oct 2006, 14:29    Post subject:  

Could you post an example of the commands you are using, please?
Back to top
View user's profile Send private message MSN Messenger 
bostonvaulter


Joined: 26 Sep 2006
Posts: 269

PostPosted: Thu 05 Oct 2006, 15:48    Post subject:  

mv icewm-1.2.28.tar.gz compiling/
mv: cannot move `icewm-1.2.28.tar.gz' to a subdirectory of itself, `compiling/icewm-1.2.28.tar.gz

I'm in /root/ and trying to move icewm.tar.gz to the directory /root/compiling.

this is actually new. I really don't know what the problem is. It is REALLY irritating though. Is it possibly because i'm using devx_510.sfs? Or because i installed vim?
Back to top
View user's profile Send private message 
bostonvaulter


Joined: 26 Sep 2006
Posts: 269

PostPosted: Thu 05 Oct 2006, 15:55    Post subject:  

Here's another example of weird behavior
Quote:

sh-3.00# ls
Choices dotpup3 gtkdiffrc my-applications my-roxapps spot
compiling ghttpd icewm-1.2.28.tar.gz my-documents puppy-reference
sh-3.00# mkdir test
sh-3.00# cd test/
sh-3.00# ls
sh-3.00# cd ..
sh-3.00# ls
Choices dotpup3 gtkdiffrc my-applications my-roxapps spot
compiling ghttpd icewm-1.2.28.tar.gz my-documents puppy-reference test
sh-3.00# mv icewm-1.2.28.tar.gz test/
sh-3.00# ls
Choices dotpup3 gtkdiffrc my-applications my-roxapps spot
compiling ghttpd icewm-1.2.28.tar.gz my-documents puppy-reference test
sh-3.00# cd test/
sh-3.00# ls
sh-3.00# cd ..
sh-3.00# ls
Choices dotpup3 gtkdiffrc my-applications my-roxapps spot
compiling ghttpd icewm-1.2.28.tar.gz my-documents puppy-reference test
sh-3.00# rmdir test/
rmdir: `test/': Directory not empty
sh-3.00# cd test/
sh-3.00# ls
icewm-1.2.28.tar.gz
sh-3.00#


edit*

okay i think i may have found the root of the problem. upon running dmesg. I see this line repeated about 50 times
Quote:
FAT: Filesystem panic (dev sda1)
fat_get_cluster: invalid cluster chain (i_pos 7863)

that would explain my usb stick is flashing so much...

edit* again

Quote:

FAT: Filesystem panic (dev sda1)
fat_get_cluster: invalid cluster chain (i_pos 7863)
EXT3-fs error (device loop1): ext3_free_branches: Read failure, inode=68567, block=290085
Aborting journal on device loop1.
EXT3-fs error (device loop1) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device loop1) in ext3_truncate: Journal has aborted
EXT3-fs error (device loop1) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device loop1) in ext3_orphan_del: Journal has aborted
EXT3-fs error (device loop1) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device loop1) in ext3_delete_inode: Journal has aborted
ext3_abort called.
EXT3-fs error (device loop1): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only


here's some more errors. maybe my cruzer mini flash drive is just bad. I wasn't able to store my options to my 512MB, but my 1GB one seemed to be working...
Back to top
View user's profile Send private message 
MU


Joined: 24 Aug 2005
Posts: 13648
Location: Karlsruhe, Germany

PostPosted: Thu 05 Oct 2006, 16:47    Post subject:  

you might try to run "sync" after "mv".
Puppys filesystem is hold in Ram, so strange behaviour of unionfs might explain your strange results (though I'm not shure).

When I use file-operations in scripts, I always use sync to be shure all data are written to the final locations.

Mark
Back to top
View user's profile Send private message Visit poster's website 
bostonvaulter


Joined: 26 Sep 2006
Posts: 269

PostPosted: Sun 08 Oct 2006, 20:26    Post subject:  

sync, hasn't really helped for me. I deleted my pupsave.3fs file and everything on my primary usb stick, then created the save file on the empty usb stick.

Then everything was working okay for a few days. But now I've just started having the same problem. I'm thinking it might be from installing vim.

also i just got a new error in dmesg

Quote:
attempt to access beyond end of device
sdb1: rw=1, want=1000045, limit=999874
attempt to access beyond end of device
sdb1: rw=1, want=1000370, limit=999874
attempt to access beyond end of device
sdb1: rw=1, want=1000380, limit=999874
attempt to access beyond end of device
sdb1: rw=1, want=1000416, limit=999874


can anyone explain how i might try fixing that?
Back to top
View user's profile Send private message 
GuestToo
Puppy Master

Joined: 04 May 2005
Posts: 4078

PostPosted: Sun 08 Oct 2006, 21:43    Post subject:  

you could try chkdsk or scandisk from Windows

or you could boot Puppy in ram only, and type:

fsck.vfat -vf /dev/sdb1
Back to top
View user's profile Send private message 
ddtd

Joined: 03 Oct 2006
Posts: 8

PostPosted: Mon 09 Oct 2006, 06:01    Post subject:  

I have the same problem, mv and cp is not working in console, but i can copy and move using file manager.
Back to top
View user's profile Send private message 
col

Joined: 04 Jul 2006
Posts: 10

PostPosted: Tue 17 Apr 2007, 22:25    Post subject:  

I managed to solve this by doing the following:

unmount the drive with the problem (or boot puppy to RAM)
in a terminal screen type 'dosfsck -av /dev/hda2'

This is essentially what GuestToo suggested except the fsck.vfat isn't in puppy 2.00 (might be in a more recent version though)
Back to top
View user's profile Send private message 
GuestToo
Puppy Master

Joined: 04 May 2005
Posts: 4078

PostPosted: Tue 17 Apr 2007, 23:01    Post subject:  

Puppy 214 seems to have:

# where fsck
/sbin/dosfsck
/sbin/e2fsck
/sbin/fsck
/sbin/fsck.ext2
/sbin/fsck.ext3
/sbin/fsck.minix
/sbin/fsck.msdos
/sbin/fsck.reiserfs
/sbin/fsck.vfat
/sbin/reiserfsck
#
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 1 of 1 [10 Posts]  
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » House Training » Beginners Help ( Start Here)
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0759s ][ Queries: 14 (0.0374s) ][ GZIP on ]