앵앵

유저 변경(생성/수정/삭제)시  자동으로 /etc/group-, /etc/passwd-, /etc/shadow-  3개의 백업파일이 생성됨

ㅁ gvfs : gnome에서 제공하는 기능으로, gvfs-mkdir , gvfs-mount 같은 명령어로 사용자별로 fs를 mount 하거나 

            디렉토리를 생성할때 사용하는 기능

1) gvfs-mkdir : gvfs-mkdir makes a directory specified by an URI using the VFS system.

URI를 사용하는 VFR(samba,nfs등가상의 파일시스템)을 mkdir하여 사용하기 위한 command

2) gvfs-mount :  mount, unmount and list file systems using the VFS system

 ㅁ gvgs 사용으로 인한 파생현상

- 상황 : root유저로 콘솔로그인 접속한 상황에서,  일반유저가 df -k 수행시  

 일반유저로 df -k 실행시 “/root/.gvfs: Permission denied”  발생.

- 조치 : 

1)콘솔로그인한 GUI환경의 root계정을 로그아웃하면됨

   .명령어 : gnome-session-save --logout

2) umount /root/.gvfs

- 현재 rich-rule

root@system1 ~]# firewall-cmd --list-all

public (active)

  target: default

  icmp-block-inversion: no

  interfaces: ens33 ens37 ens38 ens39 team0

  rich rules: 

rule family="ipv4" service name="nfs" accept

rule family="ipv4" source address="192.168.0.200/24" forward-port port="5423" protocol="tcp" to-port="80"

-삭제시도

[root@system1 ~]# firewall-cmd --remove-rich-rule='rule family="ipv4" source address="192.168.0.200/24" forward-port port="5423" protocol="tcp" to-port="80"'

Error: %x format: a number is required, not NoneType

삭제를 시도했으나, 자꾸 포맷이 이상하다는 메세지가 뜬다.  잘못된 포맷이 없는뎅 ㅜ

-해결방법

firewall 명령으로 추가한 정책은  /etc/firewalld/ 폴더내에 .xml파일로 저장되어있다.

root@system1 ~]# firewall-cmd --list-all

public (active)

  target: default

  icmp-block-inversion: no

  interfaces: ens33 ens37 ens38 ens39 team0

  rich rules: 

rule family="ipv4" service name="nfs" accept

rule family="ipv4" source address="192.168.0.200/24" forward-port port="5423" protocol="tcp" to-port="80"

rule family="ipv4" source address="192.168.0.0/24" forward-port port="5423" protocol="tcp" to-port="80"

rule family="ipv4" source address="192.168.0.200" service name="ssh" drop

위의 public(zone), rich ruels을 삭제하고 싶으면

/etc/firewalld/zones/public.xml을 열어보자

아래 빨간색 부분을 삭제 후 저장 하면

firewall-cmd --remove-rich-rule과 같은 효과로,  rich .rule을 삭제할수 있다.

-삭제결과

1) /etc/firewalld/zones/public.xml 파일 내용

-> rule이  nfs 허용 1건이다.

2) firewall-cmd --reload         

 -> reload 수행한다

3) list 결과확인

[root@system1 zones]# firewall-cmd --list-all

public (active)

  target: default

  icmp-block-inversion: no

  interfaces: ens33 ens37 ens38 ens39 team0

  sources: 

  services: ssh dhcpv6-client nfs

  ports: 

  protocols: 

  masquerade: no

  forward-ports: 

  source-ports: 

  icmp-blocks: 

  rich rules: 

rule family="ipv4" service name="nfs" accept

rule이 1건으로  vi열어서 삭제한 아래3건은 삭제되었다.

rule family="ipv4" source address="192.168.0.200/24" forward-port port="5423" protocol="tcp" to-port="80"

rule family="ipv4" source address="192.168.0.0/24" forward-port port="5423" protocol="tcp" to-port="80"

rule family="ipv4" source address="192.168.0.200" service name="ssh" drop

※ 가상머신이므로 , 물리적인 F/O테스트는 불가함

- 준비 = teaming  (과정생략)

 teaming 구성 URL 참조 :  http://leejinae.tistory.com/16?category=767768

- 대상 interface 

 - team : team0

 - ethernet : ens38

 - ethernet : ens39

- 상태 

1) device 상태

[root@system1 network-scripts]# nmcli dev

장치   유형      상태           연결        

ens33  ethernet  연결됨         ens33       

ens37  ethernet  연결됨         ens37       

ens38  ethernet  연결됨         team0-port1 

ens39  ethernet  연결됨         team0-port2 

team0  team      연결됨         team0     

※ 장치 name (ens38,ens39) 와  연결 name team-port1, team-port2를 분명히 구분하여 기억할것

[root@system1 network-scripts]# teamdctl team0 state

setup:

  runner: activebackup

ports:

  ens38

    link watches:

      link summary: up

      instance[link_watch_0]:

        name: ethtool

        link: up

        down count: 0

  ens39

    link watches:

      link summary: down

      instance[link_watch_0]:

        name: ethtool

        link: down

        down count: 1

runner:

  active port: ens38                                    #현재 active port는 ens38

 1) port down

  [root@system1 network-scripts]# teamdctl team0 port remove ens38

 2) ethernet down 

  [root@system1 network-scripts]# ifconfig ens38 down

(ens38을 down 시켰으므로,   team 구성된 나머지하나(ens39)가 active port 가 됨)

[root@system1 network-scripts]# teamdctl team0 state

setup:

  runner: activebackup

ports:

  ens39

    link watches:

      link summary: up

      instance[link_watch_0]:

        name: ethtool

        link: up

        down count: 1

runner:

  active port: ens39

- OS : RHEL 7

- device : ens38,39로 team0 구성

- team connection 생성, ifname 생성

[root@system1 ~]# nmcli con add con-name team0 type team ifname team0 config '{"runner":{"name":"activebackup"}}'

연결 'team0' (2922ad0f-7675-4370-8f06-ce0ddfdd8bc7)이 성공적으로 추가되었습니다.

-> con-name ,   type , ifname 옵션을 확인할것

- team connnection port 생성

[root@system1 ~]# nmcli con add con-name team0-port1 type team-slave ifname ens38 master team0

연결 'team0-port1' (d8b8b8f8-0326-4517-a499-a4abfb0a82da)이 성공적으로 추가되었습니다.

[root@system1 ~]# nmcli con add con-name team0-port2 type team-slave ifname ens39 master team0

연결 'team0-port2' (d62022f2-34df-456c-85b0-99028d2f29e9)이 성공적으로 추가되었습니다.

ㅁ순서

- 대상 FS; /test

1)FS unmount 

2)FS 검사 

3)FS resize 

4)LV reduce

- 현재 FS사이즈

[root@station ~]# df -k

Filesystem              1K-blocks    Used Available Use% Mounted on

/dev/mapper/centos-root  17811456 4222804  13588652  24% /

/dev/mapper/vg00-lvol0     380533    2062    354305   1% /test

1) FS unmount

[root@station ~]# umount /test

2) FS 검사

[root@station ~]# e2fsck -f /dev/vg00/lvol0

e2fsck 1.42.9 (28-Dec-2013)

Pass 1: Checking inodes, blocks, and sizes

Pass 2: Checking directory structure

Pass 3: Checking directory connectivity

Pass 4: Checking reference counts

Pass 5: Checking group summary information

/dev/vg00/lvol0: 11/100352 files (0.0% non-contiguous), 22937/401408 blocks

3) FS resize (380M -> 290M)

[root@station ~]# resize2fs /dev/vg00/lvol0 290M

resize2fs 1.42.9 (28-Dec-2013)

Resizing the filesystem on /dev/vg00/lvol0 to 296960 (1k) blocks.

The filesystem on /dev/vg00/lvol0 is now 296960 blocks long.

4) LV reduce (380M -> 295M)

[root@station ~]# lvreduce -L 295M /dev/vg00/lvol0

  Rounding size to boundary between physical extents: 296.00 MiB.

  WARNING: Reducing active logical volume to 296.00 MiB.

  THIS MAY DESTROY YOUR DATA (filesystem etc.)

Do you really want to reduce vg00/lvol0? [y/n]: y

  Size of logical volume vg00/lvol0 changed from 392.00 MiB (98 extents) to 296.00 MiB (74 extents).

  Logical volume vg00/lvol0 successfully resized.

-> FS resize가 먼저 이루어져야함.

    LV를 먼저 reduce 해버릴 경우, FS 내 있던 Data들은 깨지게됨

[root@station ~]# mount -t ext4 /dev/vg00/lvol0 /test

- 결과

[root@station ~]# df -k

Filesystem              1K-blocks    Used Available Use% Mounted on

/dev/mapper/centos-root  17811456 4222828  13588628  24% /

/dev/mapper/vg00-lvol0     279189    2062    258184   1% /test

/test   FS는 약 280M 로 감소확인