# [root@localhost ~]# pvcreate /dev/sdb
WARNING: dos signature detected on /dev/sdb at offset 510. Wipe it? [y/n]: y
Wiping dos signature on /dev/sdb.
Physical volume "/dev/sdb" successfully created.
[root@localhost ~]# vgcreate vg_dspace /dev/sdb
Volume group "vg_dspace" successfully created
# vgdisplay vg_dspace
--- Volume group ---
VG Name vg_dspace
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 8
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 1
Open LV 0
Max PV 0
Cur PV 1
Act PV 1
VG Size <7.28 TiB
PE Size 4.00 MiB
Total PE 1907721
Alloc PE / Size 1887437 / 7.20 TiB
Free PE / Size 20284 / 79.23 GiB
VG UUID MWcmt5-QcYs-TmOK-yEWD-O5O4-uH4L-vyYuhL
[root@localhost ~]# lvcreate -L 7.2TB vg_dspace -n vc_dspace
Rounding up size to full physical extent 7.20 TiB
Logical volume "vc_dspace" created.
[root@localhost ~]# mkfs.ext4 /dev/vg_dspace/vc_dspace
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
241594368 inodes, 1932735488 blocks
96636774 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4081057792
58983 block groups
32768 blocks per group, 32768 fragments per group
4096 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848, 512000000, 550731776, 644972544
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
[root@localhost ~]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 1.8T 0 disk
├─sda1 8:1 0 1G 0 part /boot
└─sda2 8:2 0 1.8T 0 part
├─centos-root 253:0 0 50G 0 lvm /
├─centos-swap 253:1 0 6.9G 0 lvm [SWAP]
└─centos-home 253:2 0 1.8T 0 lvm /home
sdb 8:16 0 7.3T 0 disk
└─vg_dspace-vc_dspace 253:3 0 7.2T 0 lvm
sr0 11:0 1 1024M 0 rom
[root@localhost ~]# lvremove /dev/vg_dspace/vc_dspace
Do you really want to remove active logical volume vg_dspace/vc_dspace? [y/n]: y
Logical volume "vc_dspace" successfully removed
cfdisk (util-linux 2.23.2)
Disk Drive: /dev/sdb
Size: 4000787030016 bytes, 4000.7 GB
Heads: 25 Sectors per Track: 3 Cylinders: 104187162
Name Flags Part Type FS Type [Label] Size (MB)
------------------------------------------------------------------------------
sdb1 Primary Linux 2000300.01
sdb2 Primary Linux 2000487.03*
[[root@localhost ~]# vgdisplay vg_dspace
--- Volume group ---
VG Name vg_dspace
System ID
Format lvm2
Metadata Areas 2
Metadata Sequence No 3
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 0
Open LV 0
Max PV 0
Cur PV 2
Act PV 2
VG Size <3.64 TiB
PE Size 4.00 MiB
Total PE 953861
Alloc PE / Size 0 / 0
Free PE / Size 953861 / <3.64 TiB
VG UUID aLTwuw-I8Cc-JAhn-2wtB-9UQr-42Td-XuZHLk
[root@localhost ~]# pvcreate /dev/sdb1 /dev/sdb2
Physical volume "/dev/sdb1" successfully created.
Physical volume "/dev/sdb2" successfully created.
[root@localhost ~]# vgcreate vg_dspace /dev/sdb1 /dev/sdb2
Volume group "vg_dspace" successfully created
[[root@localhost ~]# lvcreate -L 3.64TB -n vc_dspace vg_dspace
Rounding up size to full physical extent 3.64 TiB
Volume group "vg_dspace" has insufficient free space (953861 extents): 954205 required.
[root@localhost ~]# lvcreate -L 3.635TB -n vc_dspace vg_dspace
Rounding up size to full physical extent <3.64 TiB
Logical volume "vc_dspace" created.
[root@localhost ~]# mkfs.ext4 /dev/vg_dspace/vc_dspace
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
243941376 inodes, 975763456 blocks
48788172 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=3124756480
29778 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848, 512000000, 550731776, 644972544
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information:
Warning, had trouble writing out superblocks.
[root@localhost ~]# mkfs.ext4 /dev/vg_dspace/vc_dspace
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
243941376 inodes, 975763456 blocks
48788172 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=3124756480
29778 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848, 512000000, 550731776, 644972544
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information:
Warning, had trouble writing out superblocks.
[ 1761.247023] sd 4:0:0:0: [sdb] tag#0 CDB: Write(16) 8a 00 00 00 00 00 e8 f1 a9 f0 00 00 02 98 00 00
[ 1761.247030] blk_update_request: I/O error, dev sdb, sector 3908151792
[ 1761.256705] sd 4:0:0:0: [sdb] Read Capacity(16) failed: Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[ 1761.256717] sd 4:0:0:0: [sdb] Sense not available.
[ 1761.257615] sd 4:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[ 1761.257621] sd 4:0:0:0: [sdb] Sense not available.
[ 1761.257790] sdb: detected capacity change from 4000787030016 to 0
[ 1761.545493] VFS: Dirty inode writeback failed for block device dm-3 (err=-5).
[ 1827.839344] scsi_io_completion: 58 callbacks suppressed
[ 1827.839358] sd 4:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[ 1827.839365] sd 4:0:0:0: [sdb] tag#0 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
[ 1846.090413] sd 4:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[ 1846.090430] sd 4:0:0:0: [sdb] tag#0 CDB: ATA command pass through(16) 85 06 2c 00 00 00 00 00 00 00 00 00 00 00 e5 00
.
[root@box ~]# yum -y install xrdp
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
* base: centos.serverspace.co.uk
* epel: mirrors.coreix.net
* extras: mirror.sov.uk.goscomb.net
* updates: mirror.sov.uk.goscomb.net
Resolving Dependencies
--> Running transaction check
---> Package xrdp.x86_64 1:0.9.10-1.el7 will be installed
--> Processing Dependency: xrdp-selinux = 1:0.9.10-1.el7 for package: 1:xrdp-0.9.10-1.el7.x86_64
--> Processing Dependency: xorgxrdp for package: 1:xrdp-0.9.10-1.el7.x86_64
--> Running transaction check
---> Package xorgxrdp.x86_64 0:0.2.10-4.el7 will be installed
--> Processing Dependency: xorg-x11-server-Xorg(x86-64) = 1.20.4 for package: xorgxrdp-0.2.10-4.el7.x86_64
---> Package xrdp-selinux.x86_64 1:0.9.10-1.el7 will be installed
--> Finished Dependency Resolution
Error: Package: xorgxrdp-0.2.10-4.el7.x86_64 (epel)
Requires: xorg-x11-server-Xorg(x86-64) = 1.20.4
Installed: xorg-x11-server-Xorg-1.20.1-5.6.el7_6.x86_64 (@updates)
xorg-x11-server-Xorg(x86-64) = 1.20.1-5.6.el7_6
Available: xorg-x11-server-Xorg-1.20.1-3.el7.x86_64 (base)
xorg-x11-server-Xorg(x86-64) = 1.20.1-3.el7
Available: xorg-x11-server-Xorg-1.20.1-5.el7.x86_64 (updates)
xorg-x11-server-Xorg(x86-64) = 1.20.1-5.el7
Available: xorg-x11-server-Xorg-1.20.1-5.1.el7.x86_64 (updates)
xorg-x11-server-Xorg(x86-64) = 1.20.1-5.1.el7
Available: xorg-x11-server-Xorg-1.20.1-5.2.el7_6.x86_64 (updates)
xorg-x11-server-Xorg(x86-64) = 1.20.1-5.2.el7_6
Available: xorg-x11-server-Xorg-1.20.1-5.3.el7_6.x86_64 (updates)
xorg-x11-server-Xorg(x86-64) = 1.20.1-5.3.el7_6
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigestyum -y install https://archive.fedoraproject.org/pub/archive/epel/7/x86_64/Packages/x/xorgxrdp-0.2.9-1.el7.x86_64.rpm then yum -y install xrdpand it works – zigarn 15 hours ago<?php
function hh($errno, $errstr, $errfile, $errline ) {
throw new ErrorException($errstr, $errno, 0, $errfile, $errline);
}
set_error_handler("hh");
$dual = new COM("ADODB.Connection", null, CP_UTF8);
$dual->Open("dual_odbc", "uid", "password");
$sql = "SELECT top 10 *, FROM cousched where ser_no <= '20000' ";
// $c_course = odbc_exec($dual, $sql);
try {
$rs = $dual->execute($sql);
while(!$rs->eof) {
echo $rs->fields("cou_cname")->value()."<br>\n";
$rs->movenext();
}
} catch (Exception $e) {
echo nl2br($e->getMessage())."<br>\n";
echo nl2br($e->getTraceAsString());
exit;
}
$dual->close();
上面的程式，有加上 error handler 的處理。可以參考下面的連結Source: Microsoft OLE DB Provider for ODBC Drivers
Description: [Microsoft][ODBC SQL Server Driver][SQL Server]關鍵字 'FROM' 附近的語法不正確。
#0 E:\Inetpub\wwwroot\ajtest\ado_tst.php(17): com->execute('SELECT top 10 *...')
#1 {main};
應急時，在使用上，蠻方便的。$SQL = "select * from course where cou_no=? ";
$params = array($cou_no);
new COM("ADODB.Connection", null, CP_UTF8);
$cmd = new COM("ADODB.Command", null, CP_UTF8);
$cmd->CommandText = $SQL;
$cmd->ActiveConnection = $conn;
$rs = $cmd->Execute($ra, $params, 1);
$cmd->cancel();
# fsck.ext3 -pf /dev/sb1
/dev/sdb1: |======================= | 95.0%
酷吧:) 5079 5007 47 00:55 pts/1 00:08:25 /sbin/fsck.ext3 -yv /dev/hda2
# time fsck.ext4 -yfD /dev/sb1
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 3A: Optimizing directories
Rebuilding directory: |========= - 29.2% 144001413
網友向廠商詢問確認，皓月 255 使用的火星塞型號，跟 s-max 使用一樣的型號。CPR8EAGP-「」-- 白金，CPR8EAIX-「」-- 銥合金。9S -- 特長牙，尺寸為，螺絲徑：10mm，螺絲長：19mm，六角對邊：16mm。
網友使用的體驗，將白金火星塞換成釕合金的火星塞後，怠速變的更綿密，有一瞬間讓人心木以為是雙缸車，加速反應也變好。另外，因為引擎熱氣很高，特地換冷熱值更冷的，這樣廢熱也有改善。
他的使用心得，讓我很心動，不過問車行，他認為 -- 以我的使用狀況用一般白金火星塞即可， 貴金屬火星塞比較不適合通勤慢速使用。
可是我還是很想試試，終究一顆只要幾百元而已。只是火星塞有分短牙、長牙、特長牙，9S 是特長牙，若沒有確定規格，換錯了，引擎就毀了。
