Hello,
When I run following script
#!/bin/bash
cd ~/directory1
mv `ls -trF | grep -v / | tail -10 ` ~/directory2
works fine with filenames not having any space but runs into issues with filenames that have spaces tried with $file variable still doesnot work. Can someone help me (4 Replies)
Hi
I am having difficulty copying files from one dir to another due to a space in the names of the file with an extension .rtf
There are a group of files and the command am using is
cp `ls -rt /wlblive/home/whiops/ops/RTFs/*.rtf|head -20` /wlblive/home/jamshed
Since the files are... (3 Replies)
I have a text file containing files in a directory structure i.e.
/project/hr/raw/jcpdatav/datav_aug03
/project/hr/raw/jcpdatav/comb8121sep02n
/project/hr/raw/jcpdatav/datav_feb04_ons
/project/hr/raw/jcpdatav/corpsick_jun06
/project/hr/raw/jcpdatav/jcpjoiners200507... (3 Replies)
Hi,
I've a problem. Here is the code:
#!/bin/ksh
echo "enter a file name"
read a
cd /home/linux1/sam
if
then
echo "file exists"
cp $a $a_bkp
else
echo "file doesn't exist"
fi
when executed the o/p is:
enter a file name
contact
file exists
cp: missing destination file (4 Replies)
Hi,
I have files with filenames as below.
SGM Daily Sales Email-en-us-05312012.xlwa
I want to rename it in .xls. I am writing a script to change this, as there can be multiple files in subfolders.
I have the following script.
#!/bin/ksh
for oldfile in $(find... (1 Reply)
Hello
I am copying a tar from windows7 to Solaris with filezilla i could see, some characters in the name of the file get deleted.
I could see only substring of the filename
eg: original filename :abcdefghijklmnopqrstu.h
i can see like abcdefghijklm
solution to this problem is highly... (2 Replies)
Hi ,
I'm trying to move/copy the files inside the loop into a directory .
I tried the below code and the issue is the data is not copying into the created directory but the files are copying into another file
file_path="/home/etc"
Last_Day=20130930
mkdir $file_path/ARC_${Last_Day}
... (3 Replies)
Hi,
I have a list of filenames in the format with Spaces in the filename.
As an example :
Sample File 1.txt
Sample File 2.txt
Sample File 3.txt.....I have about 100 files like this.
I am trying to create a block of code or use an available command to a) Create a file b) Put in some... (2 Replies)
I have a folder with files and I have to process them in a loop. However the filenames have space characters, so the list get split.
$ touch "File Number_1"
$ touch "File Number_2"
$ ls "/tmp/File Number"_*
/tmp/File Number_1 /tmp/File Number_2
I tried following (sorry for using the... (3 Replies)
Hello,
I wrote a simple script, that basically wait for a *.dat-file in a certain folder, which is always a zipped file and extracts it.
It worked before and i changed nothing in the script, but since last week i have the problem, that it doesnt extract files containing a space. How do i make... (4 Replies)
Discussion started by: blend_in
4 Replies
LEARN ABOUT FREEBSD
recoverdisk
RECOVERDISK(1) BSD General Commands Manual RECOVERDISK(1)NAME
recoverdisk -- recover data from hard disk or optical media
SYNOPSIS
recoverdisk [-b bigsize] [-r readlist] [-s interval] [-w writelist] source [destination]
DESCRIPTION
The recoverdisk utility reads data from the source file until all blocks could be successfully read. If destination was specified all data
is being written to that file. It starts reading in multiples of the sector size. Whenever a block fails, it is put to the end of the work-
ing queue and will be read again, possibly with a smaller read size.
By default it uses block sizes of roughly 1 MB, 32kB, and the native sector size (usually 512 bytes). These figures are adjusted slightly,
for devices whose sectorsize is not a power of 2, e.g., audio CDs with a sector size of 2352 bytes.
The options are as follows:
-b bigsize
The size of reads attempted first. The middle pass is roughly the logarithmic average of the bigsize and the sectorsize.
-r readlist
Read the list of blocks and block sizes to read from the specified file.
-s interval
How often we should update the writelist file while things go OK. The default is 60 and the unit is "progress messages" so if things
go well, this is the same as once per minute.
-w writelist
Write the list of remaining blocks to read to the specified file if recoverdisk is aborted via SIGINT.
The -r and -w options can be specified together. Especially, they can point to the same file, which will be updated on abort.
OUTPUT
The recoverdisk utility prints several columns, detailing the progress
start Starting offset of the current block.
size Read size of the current block.
len Length of the current block.
state Is increased for every failed read.
done Number of bytes already read.
remaining Number of bytes remaining.
% done Percent complete.
EXAMPLES
# recover data from failing hard drive ada3
recoverdisk /dev/ada3 /data/disk.img
# clone a hard disk
recoverdisk /dev/ada3 /dev/ada4
# read an ISO image from a CD-ROM
recoverdisk /dev/cd0 /data/cd.iso
# continue reading from a broken CD and update the existing worklist
recoverdisk -r worklist -w worklist /dev/cd0 /data/cd.iso
# recover a single file from the unreadable media
recoverdisk /cdrom/file.avi file.avi
# If the disk hangs the system on read-errors try:
recoverdisk -b 0 /dev/ada3 /somewhere
SEE ALSO dd(1), ada(4), cam(4), cd(4), da(4)HISTORY
The recoverdisk utility first appeared in FreeBSD 7.0.
AUTHORS
The original implementation was done by Poul-Henning Kamp <phk@FreeBSD.org> with minor improvements from Ulrich Sporlein <uqs@FreeBSD.org>.
This manual page was written by Ulrich Sporlein.
BUGS
Reading from media where the sectorsize is not a power of 2 will make all 1 MB reads fail. This is due to the DMA reads being split up into
blocks of at most 128kB. These reads then fail if the sectorsize is not a divisor of 128kB. When reading a full raw audio CD, this leads to
roughly 700 error messages flying by. This is harmless and can be avoided by setting -b to no more than 128kB.
recoverdisk needs to know about read errors as fast as possible, i.e. retries by lower layers will usually slow down the operation. When
using cam(4) attached drives, you may want to set kern.cam.XX.retry_count to zero, e.g.:
# sysctl kern.cam.ada.retry_count=0
# sysctl kern.cam.cd.retry_count=0
# sysctl kern.cam.da.retry_count=0
BSD October 1, 2013 BSD