Doesn't appear to be anything holding it lsof returns nothing. This is a new disk, all we did was allocate it, encrypt it, put a file on it, reboot. -----Original Message----- From: Zenon Panoussis [mailto:oracle@xxxxxxxxxxxxxxx] Sent: Monday, November 27, 2006 9:44 AM To: dm-crypt@xxxxxxxx Subject: Re: Question for newbie Bates, Bob wrote: > # cryptsetup remove test201 > Error: Could not remove /dev/mapper/test201, still in use? Check what's holding it and kill it: lsof /dev/mapper/test201 kill -9 <offending_process_PID> What is strange is that something would be accessing the device after a reboot. Is it referenced in your startup scripts? Z -- The best defence against logic is ignorance. The next best is stupidity. Both can be used simultaneously. --------------------------------------------------------------------- dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/ To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx For additional commands, e-mail: dm-crypt-help@xxxxxxxx
