search for: 280g

Displaying 7 results from an estimated 7 matches for "280g".

Did you mean: 280
2009 Mar 06
2
Disk Partitioning Questions....
I am working on starting Virtural Servers at my office and have questions regarding disk partitioning recommendations. I am using SLES 10 SP2..... RAID 5.... 280G available... no external storage... 1 - Should the DOM be on primary partition and then place the VM''s in LVM? 2 - Should I create partitions in the LVM for each of my VM''s separately or can they all reside on the same partition in the LVM Volume? Thanks in advance for any inp...
2014 Jul 12
3
Syslinux 6.03pre18 cannot boot kernel from btrfs
...;. Thus the problem either corrupted vmlinuz or, most likely, syslinux does not read btrfs filesystem correctly. I mounted my root partition and here is filefrag information about /boot/* files [2]. Note to physical file offsets for vmlinuz and initramfs, it is about 10^12 bytes and corresponds to 280G on /dev/sda1. This number makes sense as my sda harddrive is 500G. syslinux also reports numbers, see [1]. It says "EDD...." and I believe the third field is disk offset, right? If so the number looks suspiciously large, it is ~10^17. Could it be that syslinux has some kind of integer ov...
2014 Jul 18
1
Syslinux 6.03pre18 cannot boot kernel from btrfs
...most likely, syslinux does not > > read btrfs filesystem correctly. > > > > I mounted my root partition and here is filefrag information about > > /boot/* files [2]. Note to physical file offsets for vmlinuz and > > initramfs, it is about 10^12 bytes and corresponds to 280G on > > /dev/sda1. This number makes sense as my sda harddrive is 500G. > > > > syslinux also reports numbers, see [1]. It says "EDD...." and I > > believe the third field is disk offset, right? If so the number looks > > suspiciously large, it is ~10^17. Coul...
2009 Oct 30
0
Does refreservation sit on top of usedbydataset?
...m curios how space is counted for this particular system (opensolaris b118) #zfs list NAME____________________ USED__AVAIL__REFER__MOUNTPOINT zsan0____________________3.10T__2.25T____23K__/zsan0 zsan0/fs__________________ 3.10T__2.25T__6.90G___/zsan0/fs [b]zsan0/fs/bar-001__________ 680G__2.65T__ 280G[/b] zsan0/fs/dnd01-sqldb______ 236G__2.45T__35.8G zsan0/fs/evg-001-sqldb____ 219G__2.45T__18.5G zsan0/fs/jen-001-sqldb____ 374G__2.55T__74.4G zsan0/fs/meg-flt001_______811G__2.84T__ 211G zsan0/fs/sfc-001__________ 229G__2.45T__29.3G zsan0/fs/sscc-001_________278G__2.45T__78.0G zsan0/fs/tph-001_____...
2007 Mar 02
1
smbfs gzip/bzip2 "File too large"?
...l file system, it is OK , but when I mount the smbfs: # df -h Filesystem Size Used Avail Use% Mounted on /dev/sda1 32G 20G 11G 64% / none 1013M 0 1013M 0% /dev/shm /dev/sdb1 135G 46G 82G 36% /data //store/homes 307G 27G 280G 9% /mnt/host The process exit by error like this: 2007-03-02 10:44:16 fs_backup ERROR gzip: stdout: File too large tar: /mnt/host/fs_backup/at_pages/at_pages.full.20070302-094405.tgz: Wrote only 8192 of 10240 bytes tar: Error is not recoverable: exiting now I also tried to wrap bzip2 instead of...
2005 Oct 18
0
[Bug 3186] New: Surprisingly large unshared memory usage
...n files (400K of those file are actually hardlinked to each other on the sending machine, and remain that way on the receiving machine---and in fact all but about 30 of them haven't changed, so virtually all 2.4M of those files also wind up hardlinked to the --link-dest directory; this is about 280G total). It takes about 10 minutes to scan a filesystem of this size, and both the sending & receiving machines rsyncs slowly expand to about 200M during this scan; that's understandable. But then, as soon as the scan is done, the second rsync process on the receiving side inflates (over t...
2014 Jul 18
0
Syslinux 6.03pre18 cannot boot kernel from btrfs
...er corrupted vmlinuz or, most likely, syslinux does not > read btrfs filesystem correctly. > > I mounted my root partition and here is filefrag information about > /boot/* files [2]. Note to physical file offsets for vmlinuz and > initramfs, it is about 10^12 bytes and corresponds to 280G on > /dev/sda1. This number makes sense as my sda harddrive is 500G. > > syslinux also reports numbers, see [1]. It says "EDD...." and I > believe the third field is disk offset, right? If so the number looks > suspiciously large, it is ~10^17. Could it be that syslinux has...