Please help!?
a couple of questions:
As some of you may have seen, I've been having a little bit of problems with ZFS lately.
http://www.opensolaris.org/jive/thread.jspa?messageID=62919
And I don't know what to do.
I am at a point where I can't sleep because I am thinking about it and trying to figure out what to do; and it's gotten so bad that I am bringing in combinatorial mathematics to permutate through my drive configuration (currently anywhere between 2-8 million permutations).
A couple of questions:
1) How is it possible that the first drive that the installation picked up was c0t7d0? (outside of depending on how the ports are scanned on the Adaptec 21610SA 16 port SATA HBA). b) Is that scan pattern always the same?
2) Is there a way to find out the order that the drives were scanned in during installation?
3) Is there a way to search for a text string inside a file recursively through a directory structure (i.e. akin to Windows search containing text)?
I am thinking/hoping that there would be some way for me to NOT have to permutate through the 2-8 M permutations because it's Solaris; and I think that there's got to be some way that the most advanced OS in the world can prevent me from having to something like that (save my stupidity, and about 140 GB of data built over 5 months that I do not have backups for).
Please help!?
[1425 byte] By [
Ewen.Chan] at [2007-11-26 10:38:42]
# 1
Is there a way to search for a text string inside a file recursively through a directory structure (i.e. akin to Windows search containing text)?
Is this all you need?
If so you could write a rather simple perl script to do it. Or I am sure there are utilities on line you could download.
Truthfully I have never once 'needed' to do such a task. Heck, it may be built in but as I said I have never even looked for one.
# 3
3) Is there a way to search for a text string inside a file recursively through a directory structure (i.e. akin to Windows search containing text)?
The below shell script if run from the directory where you want to search a string can help you in searching for a test string inside the directory recursively. You will have to pass the search string as a argument to the shell script. Though I don't know whether it is a optimal solution. If this is not which you require please ignore it.
thanks & regards
rathi
a=`find ./`
result=""
searchString=$1
for i in $a
do
grep -i $searchString $i
if [ $? -eq 0 ]
then
result="$result$i"
fi
done
echo $result
rathi at 2007-7-7 2:50:02 >
# 4
> I am thinking/hoping that there would be some way for
> me to NOT have to permutate through the 2-8 M
> permutations because it's Solaris; and I think that
> there's got to be some way that the most advanced OS
> in the world can prevent me from having to something
> like that (save my stupidity, and about 140 GB of
> data built over 5 months that I do not have backups
> for).
I can't think of any reason that permuting would help you. ZFS does *not* care about attachment order. The problem you have must be something other than that. No one has suggested that you change the order of the drives. Just that you check that the act of plugging and unplugging hasn't wiggled a wire loose or something.
If the hardware is in working condition, then it's possible that this is the result of a bug somewhere. I doubt that even if you could guarantee that the disks were in the exact same order that it would help. Unfortunately, working around it is likely going to require some of the engineers or others that are much more familiar with the ZFS code. My best suggestion is to continue to ask on the ZFS list to see if someone can look through your core files.
It is possible to search the raw disk devices for text strings, but the blocks containing them may not be near other blocks in the file. In fact, in a raidz configuration you're guaranteed that they're not near each other because they're striped across all the disks. However, you could recover snippets of text files this way.
--
Darren
