search for: 169m

Displaying 4 results from an estimated 4 matches for "169m".

Did you mean: 169
2001 Nov 19
2
df report
...9; shows: Filesystem Size Used Avail Use% Mounted on /dev/hda1 61M 5.0M 52M 9% /boot so I changed the <type> to "ext3" in fstab, rebooted and now 'df -h' shows: Filesystem Size Used Avail Use% Mounted on /dev/hda3 9.0G 169M 8.3G 2% / /dev/hda1 61M 5.0M 52M 9% /boot as expected. Running 'mount' on the <type> "auto" mounted system gives: /dev/hda3 on / type auto (rw,errors=remount-ro,errors=remount-ro) proc on /proc type proc (rw) devpts on /dev/pts type devpts (rw,gid=5,m...
2006 Apr 28
4
ZFS RAID-Z for Two-Disk Workstation Setup?
After reading the ZFS docs it does appear that RAID-Z can be used on a two-disk system and I was wondering if the system would [i]basically [/i]work as Intel''s Matrix RAID for two disks? [u] Intel Matrix RAID info:[/u] http://www.intel.com/design/chipsets/matrixstorage_sb.htm http://techreport.com/reviews/2005q1/matrix-raid/index.x?pg=1 My focus with this thread is some
2023 Jul 04
1
remove_me files building up
Thanks for the clarification. That behaviour is quite weird as arbiter bricks should hold?only metadata. What does the following show on host?uk3-prod-gfs-arb-01: du -h -x -d 1?/data/glusterfs/gv1/brick1/brickdu -h -x -d 1?/data/glusterfs/gv1/brick3/brickdu -h -x -d 1 /data/glusterfs/gv1/brick2/brick If indeed the shards are taking space -?that is a really strange situation.From which version
2023 Jul 05
1
remove_me files building up
...-b9fc-660d12c2a046 11G /data/glusterfs/gv1/brick3/brick root at uk3-prod-gfs-arb-01:~# du -h -x -d 1 /data/glusterfs/gv1/brick2/brick 12G /data/glusterfs/gv1/brick2/brick/.glusterfs 110M /data/glusterfs/gv1/brick2/brick/scalelite-recordings 3.1M /data/glusterfs/gv1/brick2/brick/mytute 169M /data/glusterfs/gv1/brick2/brick/.shard 0 /data/glusterfs/gv1/brick2/brick/.glusterfs-anonymous-inode-d3d1fdec-7df9-4f71-b9fc-660d12c2a046 12G /data/glusterfs/gv1/brick2/brick Also, this is the du -sh output for the specific directory that appears to be taking up space on brick 3: root...