Umount es tarhely problema :)

Fórumok

Van egy olyan problemam amit nem igen ertek es nem igen tennek prod gepen addig semmit, ameddig nem vagyok benne biztos, hogy lehet ezt megoldani.

ls -la /var/ftp/
total 24
drwxr-xr-x 5 root root 4096 Sep 15 15:22 .
drwxr-xr-x 25 root root 4096 Jan 21 2011 ..
drwxr-xr-x 2 root root 4096 Apr 16 2012 CentOS_6.2
drwxr-xr-x 11 root root 4096 May 30 2013 pub
drwxrwxr-- 2 root root 4096 Sep 15 15:05 RHEL5_5

Torolni akartam a RHEL5_5 konyvtarat, de nem engedi a rendszer, mert "busy".

Neztem lsof, ps -ef, ps -ax-szel, fuser /var/ftp/RHEL5_5-tel, de sehol semmi.
Kicsit kutakodtam neten, es mondtak azt is valahol, nezem meg mountot is.

A mount parancsi kiad egy ilyet:

mount
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/sda1 on /boot type ext3 (rw)
tmpfs on /dev/shm type tmpfs (rw)
/dev/sdb1 on /data type ext3 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)
/data/datashare/RHEL5_5 on /var/ftp/RHEL5_5 type none (rw,bind)

df igy nez ki:
df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
24G 21G 2.1G 91% /
/dev/sda1 99M 13M 82M 13% /boot
tmpfs 2.0G 0 2.0G 0% /dev/shm
/dev/sdb1 498G 406G 67G 86% /data

Fstab igy nez ki:
cat /etc/fstab
/dev/VolGroup00/LogVol00 / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
/dev/VolGroup00/LogVol01 swap swap defaults 0 0
LABEL=datastore /data ext3 defaults 1 1

Mi a franc ez ?
Amitol felek illetve nem is tudok, hogy ha kiadnam az umount parancsot a /var/ftp/RHEL5_5, nehogy leszedje a /data-t, mert akkor megszunik eleg sok minden letezni, pl. samba share.
Tartalma ugye mar nincs benne a konyvtarba, de a hely nem szabadult fel, eselyes ezert, mert ez meg fogja.
A mappa tartalma elerheto ott a datashare-n belul meg az RHEL5_5 konyvtarban(+csinaltam mentest is biztonsag edveert, bar kizartnak tartom, hogy hasznalnak meg 5.5-ot).

Please help :)

A cel ugye a tarhely megszerzese :)

Hozzászólások

Itt az egyik konyvtar /data/datashare/RHEL5_5 tartalma van bemountolva a másik alá: /var/ftp/RHEL5_5

Szóval fizikailag /data/datashare/RHEL5_5 foglalja a helyet. Viszont ha nem tudod umountolni akkor valami tényleg fogja, esetleg lsof se ártana.

Fedora 22, Thinkpad x220

Erre most figyeltem fel:
"Torolni akartam a RHEL5_5 konyvtarat, de nem engedi a rendszer, mert "busy"."

Mivel az a konyvtar mount point, nem tudod torolni elob kell ra egy umount, de akkor mar ugye nem ott lesz hanem az eredeti helyen a /data/datashare/ ben.

Fedora 22, Thinkpad x220

bind mount, a mount kimenetébe oda is van írva.

manból


       The bind mounts.
              Since Linux 2.4.0 it is possible to remount part of the file hierarchy somewhere else. The call is
                     mount --bind olddir newdir
              or shortoption
                     mount -B olddir newdir
              or fstab entry is:
                     /olddir /newdir none bind

              After this call the same contents is accessible in two places.  One can also remount  a  single  file  (on  a  single
              file). It's also possible to use the bind mount to create a mountpoint from a regular directory, for example:

                     mount --bind foo foo

              The  bind  mount  call attaches only (part of) a single filesystem, not possible submounts. The entire file hierarchy
              including submounts is attached a second place using

                     mount --rbind olddir newdir

              or shortoption

                     mount -R olddir newdir

              Note that the filesystem mount options will remain the same as those on the  original  mount  point,  and  cannot  be
              changed  by  passing  the -o option along with --bind/--rbind. The mount options can be changed by a separate remount
              command, for example:

                     mount --bind olddir newdir
                     mount -o remount,ro newdir

              Note that behavior of the remount operation depends on the /etc/mtab file. The first command stores the  'bind'  flag
              to  the  /etc/mtab  file  and  the  second  command  reads  the flag from the file.  If you have a system without the
              /etc/mtab file or if you explicitly define source and target for the remount command (then  mount(8)  does  not  read
              /etc/mtab), then you have to use bind flag (or option) for the remount command too. For example:

                     mount --bind olddir newdir
                     mount -o remount,ro,bind olddir newdir

              Note that remount,ro,bind will create a read-only mountpoint (VFS entry), but the original filesystem suberblock will
              be still writable, it means that the olddir will be writable, but the newdir will be read-only