Case insensitive NSS volume on cluster

We are trying to migrate from Apache2 running on a Netware server to a OES2 Linux server running on a two node cluster. The Cluster Volume is NSS and when Apache runs we appear to have a case sensitivity issue. I have read on the Forums that NSS can be configured to be case insensitive but I am unsure how I change the cluster to mount NSS case insensitive.
Can anyone assist? (It would sure help because trying to change all of the folders and files to lowercase and change all of the .php scripts to load the lowercase folders has been a nightmare!)
Thanks for any information that you can provide!
Charlie
~~~

Originally Posted by utman
I found an OES 1 doc that says if you add the long namespace it will make it case insensitive.
Novell Documentation
Any idea if I LOSE anything by mounting it with Long Namespace? I have never been quite sure WHY you would want it to be Case Sensitive in Linux. It just seems to make for a lot of confusion. (HOME vs. home)

Similar Messages

How do I move my large iTunes collection from a case-sensitive hard drive to a case-insensitive hard drive?

I currently keep my iTunes media on an external hard drive because it takes up too much space on my machine. I recently discovered that it was formatted as case-sensitive when I bought it, and now months later I'm having issues. When attempting to back up my files on a case-insensitive hard drive, the operation failed due to conflicting file/folder names (Artist and artist are now considered the same file name and one would have to overwrite the other). I now have a large iTunes file collection that is stuck on the case-sensitive hard drive, and I want to save a backup on a case-insensitive drive.
Is there a way to identify all cases where multiple files/folders have the same title/album/artist but different spelling so there will be no conflicts? The folder/file names would have to be crossed referenced to highlight any cases where File/fiLe/file would cause a problem.
I imagine there is a way to do this using iTunes script or Automator or a command in terminal or something rather than going through and checking/fixing all the information for thousands of songs by hand. I'm at the limits of my minimal development skills, so any help would be appreciated.

You should be able to use either "Carbon Copy Cloner" or "SuperDuper" (free for this purpose) to copy your case-sensitive volume to an empty case-insensitive one. Make at least two such copies on different drives. One is not enough to be safe.
If there are any name conflicts—that is, files in the same folder with names that differ only in case, such as "File" and "file"—then you will either get an error or one of the files won't be copied. You must ensure either that no such conflicts exist, or that the consequences are not important. How you do that is up to you. Unless you went out of your way to create conflicts, they probably don't exist.
Then erase the source volume in Disk Utility as case-insensitive. This action will remove all data from the volume.
Restore from one of your backups using the same application you used to create it, or use the "Restore" feature of Disk Utility, which will be faster. Search its built-in help for the term "duplicate" if you need instructions.

How do I convert a case sensitive drive to a case insensitive drive?

I have recently purchased a MacMini Server, and installed the 2 internal hard drives in a RAID 0 configuration to obtain the speed and 1 TB capacity, but unfortunately (rather stupidly in retrospect) formatted the drive in case sensitive mode.
On installing the operating system and multiple applications, everything seemed to work well until I tried to install Adobe Acrobat X Pro. This application refuses to install on a case sensitive formatted drive, which I now understand is a common problem.
The question is how can I convert to a case insensitive format without reinstalling all of the software from scratch?
I have a Time Machine backup, and the easiest thing for me would be to reformat the drive, and then restore from the Time Machine backup.
Will this process work? Or will there be some complications and files that will not function if they were originally installed on a case sensitive drive?
Any help is appreciated....

iPartition can do it ( http://www.coriolis-systems.com/iPartition.php ).
from iPartition Help:
Make Case Sensitive/Case Insensitive
HFS+ now supports a case sensitive format as well as the usual case insensitive format. On a case sensitive volume, the names “Readme”, “README” and “ReadMe” would all represent different files, even if they were in the same folder.
This option allows you to non-destructively change a case sensitive volume into a case insensitive one, and vice-versa. If you are going from a case sensitive volume to a case insensitive volume, some of your files may be renamed automatically by iPartition so that they do not clash. If all of the files in the table below were in the same directory, the right hand column shows the new names iPartition would choose for them:
Old name New name
README.txt README.txt
ReadMe.txt ReadMe 1.txt
Readme.txt Readme 2.txt
README README
ReadMe ReadMe 1
Readme Readme 2
Notice that iPartition puts the number before any file extension.
N.B. iPartition does not transform filenames with numbers on the end back into their original forms. There is no way to tell which files were renamed by the user and which were renamed by the conversion process.

Commvault issue with JobResults on NSS volume

Hi all, we see an issue with Commvault 9R2 (sp10) using a Linux i-data agent client on OES2SP3 x64 backing up (clustered) NSS volumes. For speed we, this case, do not want to use a NSS i-data agent, so we just leverage the Linux i-data agent.
The issue is that if we use the Linux i-data agent and the jobresults directory is also hosted on the same NSS volume that's being backed up we get an error on failures.cvf
"Could not open failures file [/media/nss/LBAPOA/galaxy/JobResults/2/268/Failures.cvf] error number [19, No such device]. The backup would continue but this would affect the ability of reattempting the failed file backup during next incremental backup. A full backup is recommended to back up all files. Check the following: 1. The account this product uses has permissions to the product's install directory. 2. Sufficient disk space is available for the Job Results directory. If the problem persists, please upload log files from CommServe, MediaAgent and Client and contact your vendor's support hotline with the job ID of the failed job."
If we (for testing only) move only the jobresult directory to an ext3 volume we do not see the issue.
Has someone seen (and hopefully fixed) this issue before? My guess it's a Commvault issue, but just before we open a SR with them I would like to now if there's a good guess to solve this:)

sveld,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/

[KDE] Force ntfs drives to be case insensitive. How?

Hi to all,
I use KDE and I mount usb ntfs drives with the applet (no fstab configs).
I would like to configure KDE and ntfs-3g to mount ntfs drives using the mount option "windows_names" to force linux to consider that filesystem as case insensitive (as is the default under Windows XP).
Is there any config file I can use to set such an option?
Thank you,
Xwang
PS I don't know if it is the correct forum to post such a question. In case it isn't, can some moderator move the discussion to the correct forum, please?

Short Answer: No.
I did some digging and it looks like this is not possible to set in a config file.
KDE uses udisks "under the hood" to mount filesystems. In most cases, KDE just asks udisks to use its default settings. However, sometimes KDE will pass along extra mount options. For example, KDE forces udisks to use the flush option on vfat volumes as a result of this bug report (https://bugs.kde.org/show_bug.cgi?id=273792). This is all done in the source code (solid/solid/backends/udisks2/udisksstorageaccess.cpp).
UDisks has a bunch of default options, but they are also set in the source code (http://cgit.freedesktop.org/udisks/tree … lesystem.c). You could recompile with those defaults changed if you wanted to.
The KDE Solid backend for hardware has some plain text rules files in /usr/share/apps/solid/actions where you might be able to intercept KDE and insert your own program. Probably it is not worth the trouble.

Invalid descriptor error when trying to access nss volums

Hi everyone,
sorry for my english, when some users try to access shared nss volumes they get this error " invalid descriptor", but other folders are accessible at the same level.
users are on windows 7 and the last novell client.
thanks

On 23/06/2014 16:06, skaii wrote:
> sorry for my english, when some users try to access shared nss volumes
> they get this error " invalid descriptor", but other folders are
> accessible at the same level.
>
> users are on windows 7 and the last novell client.
Since you reference Novell Client I'm thinking that you're not using
Novell's Dynamic File Services product[1] which is what this forum is
for. If that is the case then you should repost in a more appropriate
forum, depending on whether you're using Open Enterprise Server (OES) or
NetWare.
HTH.
[1] http://www.novell.com/products/dynamic-file-services/
Simon
Novell Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.

Turning off case-sensitive mode in a cluster?

I just set up a cluster and installed a web application that was running on a non-clustered
machine. When I started to run the application I noticed file references to JSPs
were case sensitive. The setting during deployment of the web application to ignore
case does not seem to work in a clustered environment. Does anybody know how to
turn this off in a cluster?
-Rich

I am using weblogic 6.1 on windows 2000. When the web application is running in
a non cluster environment, it runs in the case-insensitive mode. The toggle switch
in the admin console allows the mode to change to case-sensitive.
How ever, when I deploy the web app into a cluster, it always runs in case-sensitive
mode. The setting in the admin console for the web app is ignored. How can I run
the web app in a cluster in case-insensitive mode?
Any thoughts?
=?iso-8859-1?Q?Jean=2DFran=E7ois?= Gervais <[email protected]> wrote:
Hi Rich
Filenames are case-sensitive only on UNIX, and not case-sensitive on
Win/NT.
In WLS5.1 exists a property for the case sensitivity of the jsp' extension
files.
weblogic.httpd.servlet.extensionCaseSensitive
In WLS6.1, you can configure the same property in the console (configuration/files
tab of the
webApp).
Hope this help.
JFG
rich wrote:
I just set up a cluster and installed a web application that was runningon a non-clustered
machine. When I started to run the application I noticed file referencesto JSPs
were case sensitive. The setting during deployment of the web applicationto ignore
case does not seem to work in a clustered environment. Does anybodyknow how to
turn this off in a cluster?
-Rich

Server umounts NSS volumes for no obvious reason

OES2 SP1, 2-node cluster
I had a server unmount an NSS volume with the message below in the logs.
Any ideas what could have caused this?
SAN_SERVER is the cluster pool.
USERAREA is an NSS volume in the pool.
Code:
May 21 10:21:21 vishnu ncs-resourced: resourceMonitor: SAN_SERVER.monitor failed 256
May 21 10:21:21 vishnu ncs-resourced: resourceMonitor: SAN_SERVER 1 failures in last 600 seconds
May 21 10:21:25 vishnu adminus daemon: umounting volume USERAREA lazy=1
May 21 10:21:25 vishnu adminus daemon: Failed to delete the directory /media/nss/USERAREA. Error=39(Directory not empty)
May 21 10:21:25 vishnu adminus daemon: Entries for Volume USERAREA from pool SAN are not removed during pool deactivation
May 21 10:21:25 vishnu kernel: Waiting for 2 Inuse beasts to unlink
... repeated multiple times
May 21 10:21:36 vishnu kernel: fastReadCache - Buffer's should always have an inode
May 21 10:21:36 vishnu kernel: isCached - Buffer's should always have an inode
May 21 10:21:36 vishnu kernel: isCached - Buffer's should always have an inode
... repeated multiple times

This looks as if you have a monitor script that is looking at your
resource - spots a failure and then starts a unload/load routine.
I think that your cluster monitor script has been copied from another
resource and has not been edited to reflect the change
T
On Tue, 22 May 2012 09:46:01 GMT, vimalkumar v
<[email protected]> wrote:
>
>*OES2 SP1, 2-node cluster
>*
>I had a server unmount an NSS volume with the message below in the
>logs.
>Any ideas what could have caused this?
>
>SAN_SERVER is the cluster pool.
>USERAREA is an NSS volume in the pool.
>
>
>Code:
>--------------------
> May 21 10:21:21 vishnu ncs-resourced: resourceMonitor: SAN_SERVER.monitor failed 256
> May 21 10:21:21 vishnu ncs-resourced: resourceMonitor: SAN_SERVER 1 failures in last 600 seconds
> May 21 10:21:25 vishnu adminus daemon: umounting volume USERAREA lazy=1
> May 21 10:21:25 vishnu adminus daemon: Failed to delete the directory /media/nss/USERAREA. Error=39(Directory not empty)
> May 21 10:21:25 vishnu adminus daemon: Entries for Volume USERAREA from pool SAN are not removed during pool deactivation
> May 21 10:21:25 vishnu kernel: Waiting for 2 Inuse beasts to unlink
> ... repeated multiple times
> May 21 10:21:36 vishnu kernel: fastReadCache - Buffer's should always have an inode
> May 21 10:21:36 vishnu kernel: isCached - Buffer's should always have an inode
> May 21 10:21:36 vishnu kernel: isCached - Buffer's should always have an inode
> ... repeated multiple times
>--------------------

Prevent directory move on NSS volume

This issue has come up from time to time, but never annoying enough to address until now. I have a few directories on a OES 11 server running NSS volumes that are utilized as "public" folders for users and departments. The rights that are typically granted to the top-level directory are 'RWECMF' to the OU. The issue is that on occasion, a user will accidentally go mouse crazy and inadvertently move the directory to a new location, thus causing a search and find adventure to move the directory back to the proper location.
The question is, am I missing something really basic here to allow users to continue to perform what they need to do on the file system below public, but to prevent them from the ability to move the top-level directory, in this case "public?"
Any comments would be greatly appreciated.
Thanks!

On Wed, 28 Jan 2015 13:36:02 +0000, donaldsolberg wrote:
> This issue has come up from time to time, but never annoying enough to
> address until now. I have a few directories on a OES 11 server running
> NSS volumes that are utilized as "public" folders for users and
> departments. The rights that are typically granted to the top-level
> directory are 'RWECMF' to the OU. The issue is that on occasion, a user
> will accidentally go mouse crazy and inadvertently move the directory to
> a new location, thus causing a search and find adventure to move the
> directory back to the proper location.
Yup. It happens.
The usual answers are:
1. Take the rights away.
2. Shoot the offending users. Repeat until it stops happening.
3. Use something to "tune" the mouse action on the workstation to make
moving things accidently more difficult.
Pick one... But #2 is likely to lead to other problems.
> The question is, am I missing something really basic here to allow users
> to continue to perform what they need to do on the file system below
> public, but to prevent them from the ability to move the top-level
> directory, in this case "public?"
Sadly, no. If they have sufficient rights to do so, the server doesn't
know or care why they're moving stuff from "here" to "there". It's a
valid operation, and the server does what it does as quickly as possible.
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.netiq.com
Please post questions in the forums. No support provided via email.
If you find this post helpful, please click on the star below.

Migrating GW without NSS volume

Hi,
Running GW 2012 on a NSS volume on SLES11sp3 with OES11sp2.
I want to migrate my GW (GWIA, MTA, PO, Webaccess, Messenger) to a new SLES server but I only want to use a EXT3 volume.
What is the best way to do this migration?
Regards
John

John Gill wrote:
> What is the best way to do this migration?
This is just like any other migration, except you need to see if your NSS volume
was Long Namespace, and if there is any likelihood that there are mixed case
files. If there are, then you would need to run dbcopy with the -m switch to
migrate the files to all lowercase. If the files are already all lowercase, you
could use any type of copy procedure that you like. As Laura says, though,
doing two passes to avoid downtime is useful.
Danita
Novell Knowledge Partner
Are you a GroupWise Power Administrator? Join our site.
http://www.caledonia.net/register
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...

Antivirus: clustered NSS-Volume

hi,
I'm not sure if this is the right forum, but...
we want to install Antivirus-Services (sophos) on our cluster-nodes to protect against viruses on the nss-volume.
1. Does anyone have any experience on this subject - especially on the question if it's a good idea to run the AV on the cluster-nodes (load, locking of files, behaviour on virus detection and so on.)?
2. What is the Novell-recommended way to deal with the AV-Question in a clustered environment (sles10sp3+ oes2sp3)?
would appreciate any help on this.
thx,
hugo

Am 06.07.2011 17:36, schrieb susehoush:
> we want to install Antivirus-Services (sophos) on our cluster-nodes to
> protect against viruses on the nss-volume.
>
> 1. Does anyone have any experience on this subject - especially on the
> question if it's a good idea to run the AV on the cluster-nodes (load,
> locking of files, behaviour on virus detection and so on.)?
A volume mounted as nssvol on an OES2 SP2,3 server might be scanned with
savscan like a local one. We use an entry to /etc/cron.d which is
created by the cluster load and deleted by the cluster unload script.
Cron starts a daily savscan on the cluster volume, eg:
savscan /media/nss/VOL1 -exclude $EXCL -p=$SLOGDIR/sophos-$2-$DATE
-move=$QUARANTINE --no-follow-symlinks --no-reset-atime -archive -all
-pua -nc -mime -oe
Replace the variables with suitable names. Be aware that the "-archive"
and "-all" options might slow down the scan significantly.
A savscan job will result in 100% CPU load. With todays multicore CPU
this should be OK provided that not too many are started at once. I
should add a nice statement to the call also.
Savscan interferes with our backup system. I had to add the
"--no-reset-atime" option. Without it the ctime of all files scanned
will be updated which results in the files being included in the next
incremental backup. This turns all incremental backups in full ones, of
course.
I never tried on access scanning. IMO this does not make much sense on a
file server and should be done on the clients.
> 2. What is the Novell-recommended way to deal with the AV-Question in
> a clustered environment (sles10sp3+ oes2sp3)?
I have no idea. But in general support at sophos is quite responsive.
Gnther

Reformat as case insensitive

Dear all,
I just realized that my Disk is formatted as case sensitive and seems to explain many problems that I had with adobe/corel softwares. I would like to reformat the disks in case insensitive, however, I am a bit afraid that i will not be able to recover the back ups from Time Machine (since made under another format type).
Does anybody know whether I can safely reformat my disks and correctly recover my back ups (data, software etc...) from time machine ?
Would you recommand to do this process while upgrading to Lion OS ?
Many thanks in advance for any help/suggestions,
Fredo

All I can suggest is to use something like Carbon Copy Cloner or SuperDuper! to put a bootable backup/clone onto a volume formatted as case insensitive and boot with it. If that works w/o issues, erase the case sensitive and reverse the process.

After Update, cannot delete files from nss volumes

Not sure if this is the same problem caused by the SLES11 upgrade, but after running all the upgrades on an OES11 system, I can see all the nss volumes of the upgraded servers from workstations using the Novell client, and I can copy or create files on these volumes. However, I cannot delete any files, they disappear from the workstation windows explorer when they are "deleted", but an f5 promptly shows the files are still there. I can go into the server as root, and delete the files under Linux with no problems, so this part is working OK.
I am running Novell 11.1 patch 1, and this problem has only been noticeable after the update installation.
I have supervisor rights to the volumes and files, and if I additionally set all the other file rights, I am still unable to delete the files.
Anyone got any ideas?
Cheers.
ChasR

Originally Posted by chas
Not sure if this is the same problem caused by the SLES11 upgrade, but after running all the upgrades on an OES11 system, I can see all the nss volumes of the upgraded servers from workstations using the Novell client, and I can copy or create files on these volumes. However, I cannot delete any files, they disappear from the workstation windows explorer when they are "deleted", but an f5 promptly shows the files are still there. I can go into the server as root, and delete the files under Linux with no problems, so this part is working OK.
I am running Novell 11.1 patch 1, and this problem has only been noticeable after the update installation.
I have supervisor rights to the volumes and files, and if I additionally set all the other file rights, I am still unable to delete the files.
Anyone got any ideas?
Cheers.
ChasR
I had a similar problem at updating with SP3 on SP4. It was similar, that permission ERASE is not applied to all trustees working through ncp in spite of the fact that it was available.
Has solved a problem that has redefined this permission for trustees on all catalogues.

Possible to do case-insensitive searches?

G'day,
I was wondering if it's possible to do case-insensitive searches in oracle/HTMLDB?
I've tried what I thought would work
"select * from application where name like '%microsoft%'", this unfortunately doesn't return any records with a capital in it(eg "Microsoft").
If there is no way to do case-insensitive searches what is the best way around it?
Thanks
-Colin

Colin,
Yes it is possible to do case insensitive searches using SQL. Try, for example:
select * from application where upper(name) like '%ORACLE%'
The trick is to upper() both sides of the like operator.
Sergio

Error in a report after enabling case insensitive search in conn pool prop

Hi All,
I put the below code in connection pool's connection string to enable case insensitive search.
alter session set NLS_SORT=BINARY_CI
alter session set NLS_COMP=LINGUISTIC
After putting this code one of my report started giving the below error which was working fine otherwise.
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. NQODBC SQL_STATE: HY000 nQSError: 10058 A general error has occurred. nQSError: 16001 ODBC error state: S1000 code: 1791 message: OracleODBCOraORA-01791: not a SELECTed expression. nQSError: 16001 ODBC error state: S1000 code: 1791 message: OracleODBCOraORA-01791: not a SELECTed expression. nQSError: 16015 SQL statement execution failed. (HY000)
The report gives error for the below divide condition when I select a column from a different dimension (eg: region)
COUNT(DISTINCT RMA.RMA)/COUNT(DISTINCT User."User Name")
Can anyone please throw a light why this is happening.

Below is the SQL which is throwing error in OBIEE. It was working fine when I tried running it in toad:
select T1609.ATTRIB_05 as c1,
count(distinct T1609.ATTRIB_42) as c2,
TRUNC(T1159.FSCL_WEEK_START_DT) as c3
from
WC_DAY_D T1159 /* RMA_RECEIVED_DT(WC_DAY_D) */ ,
WC_RMA_D T571,
WC_FV_FA_D T1609,
WC_FV_FA_F T1679
where ( T571.ROW_WID = T1679.RMA_WID and T1159.ROW_WID = T1679.RMA_RECEIVED_WID and T1609.ROW_WID = T1679.FV_FA_WID and T1609.ATTRIB_39 <> 'FV' and (T571.STATUS_CD in ('2nd FA', '2nd FA Review', 'Closed')) and TRUNC(T1609.TODO_ACTL_END_DT) is not null and TRUNC(T1159.FSCL_WEEK_START_DT) between TIMESTAMP '2009-03-22 00:00:00' and TIMESTAMP '2009-04-12 00:00:00' )
group by T1609.ATTRIB_05, TRUNC(T1159.FSCL_WEEK_START_DT)
order by c3
-------------------- Query Status: Query Failed: [nQSError: 16001] ODBC error state: S1000 code: 1791 message: [Oracle][ODBC][Ora]ORA-01791: not a SELECTed expression.
[nQSError: 16001] ODBC error state: S1000 code: 1791 message: [Oracle][ODBC][Ora]ORA-01791: not a SELECTed expression.
[nQSError: 16015] SQL statement execution failed.

Case insensitive NSS volume on cluster

Similar Messages

Maybe you are looking for