諸々の年払い、いろいろな物が壊れて必要部材の調達、救急車で運ばれる、MRIなど検査三昧、たらい回しなど、医療費の爆発などが重なってカードの支払額、支払いが出来なくてカードの現金化などして、付けがきた。さらに、追い打ちをかけるかのように、アパートの更新費用の請求が来た。西の方では建前上かいていあっても、払ったことはないので、そういうものだとおもっていたら、どうやら東は違うようだ。がっぽり請求、更新費、町会費、保険料などしめて13万以上。大杉。
まずは、9/27引き落としが26.5万に対して、お給料の手取り25万ちょっと。口座残高20万ちょっと。
これだけだと、大丈夫のように見えるが、通信費、光熱費、食費、医療費などを全部入れた生活費が8万円、家賃が12万円。
そして、9月に引き落としが有る分も分かっていて、来月も20万以上の引き落としが来るはず。
さらに追い打ちをかけるように、家の更新費が13万ちょいで9月中旬までに支払えと言われて、どう考えても支払えない。
入社当初の条件が、42+ボーナスで600万ちょいという条件で採用通知が出ていて、今の職を決定、家を決めたが、引っ越し終わりそうなとき、トラックを運転している最中に電話がかかってきて、ごめん、条件変更させてといわれ、支給額25万。残業代有り。毎日3時間ぐらい残業すれば、元の金額に近くなるよといわれ、渋々了承。
まあ、業務があまりにもアレ過ぎて、どのみち3時間ぐらいの残業は普通だから、どっちもどっちかなとおもったが、最後は業務であふれているのに、残業代は出ません、昇格で、残業代でないとか、で、結局さらに悪条件に。計画的深夜メンテなども、労働基準法的に定められている深夜割り増しも出ていません。一度、そこに対してつっこんで聞いてみたけど、回答が無く。ああ。黒い。さらに、ボーナスもなく、金一封。
挙げ句の果てに、オフィス引っ越し遠くなると言う噂。あの、最悪、時間が悪いと、バスを含めて、乗り換え6回なんですけど。と。ま、元事業本部長が色々とがんばってくださっていて、給与面で、一時の最悪な状態からは解決したけど、残業代があったときの方がまだ、財布が潤っていた気がする。はぁ。どうしようかね。このまま銀行でも襲うか(嘘)
そういうわけで、アルバイトを探し中。このままだと、生きていけない。
引っ越しすればいいやんとかいわれるけど、そうそう簡単に引っ越しはできません。
静岡から出てくるときに、見積額で520万超えるような見積もり。複数社相見をとったが、他の数社は見積もりですら出してこない。出してきた一社が520を超えるような見積もり。あり得ないので、ステップワゴンを借りたり、2トントラックを借りたりして自力引っ越し。そして、引っ越しオフとして、手伝ってくださった方々がいて、何とかなったけど。。現実問題引っ越しは無理ですね。敷金礼金、更新料考えると、どうしようも有りません。
というわけで、アフィリエイトをばんばんクリックしていって、バナーにある物を契約、購入していってください。そうすれば、何とか生きていけるようになるかもしれません。
GoogleAdsenceは現金化することにしました。円高だから、今この手を使いたくないんだけど...かなり説破詰まっています。ぎりぎり。
本当に色々とついていないというか、だまされやすいというか...
確か、これは、ドスパラで買ったハードディスクだったような。。。
一応2年はもったのかな・・・?
確か、BOXで買っているので、3年保証モデル。早めに交換しないとなぁ...
Sep 25 21:39:53 storage01 scsi: [ID 365881 kern.notice] /pci@0,0/pci8086,2944@1c,2/pci103c,322b@0 (mpt1):
Sep 25 21:39:53 storage01 Log info 0x31130000 received for target 4.
Sep 25 21:39:53 storage01 scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc
root@storage01:~/smartmontools-5.40# ./smartctl -a /dev/rdsk/c4t4d0
smartctl 5.40 2010-10-16 r3189 [i386-pc-solaris2.11] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Model Family: Hitachi Deskstar 7K2000
Device Model: Hitachi HDS722020ALA330
Serial Number: JK1175YAXXXXXX
Firmware Version: JKAOA3EA
User Capacity: 2,000,398,934,016 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Tue Sep 25 22:58:49 2012 JST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: FAILED!
Drive failure expected in less than 24 hours. SAVE ALL DATA.
See vendor-specific Attribute list for failed Attributes.
General SMART Values:
Offline data collection status: (0x84) Offline data collection activity
was suspended by an interrupting command from host.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (23359) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 255) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 059 059 016 Pre-fail Always - 90973161
2 Throughput_Performance 0x0005 131 131 054 Pre-fail Offline - 107
3 Spin_Up_Time 0x0007 124 124 024 Pre-fail Always - 559 (Average 610)
4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 17
5 Reallocated_Sector_Ct 0x0033 001 001 005 Pre-fail Always FAILING_NOW 1818
7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 119 119 020 Pre-fail Offline - 36
9 Power_On_Hours 0x0012 098 098 000 Old_age Always - 18530
10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 17
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 45
193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 45
194 Temperature_Celsius 0x0002 166 166 000 Old_age Always - 36 (Min/Max 20/51)
196 Reallocated_Event_Count 0x0032 004 004 000 Old_age Always - 1932
197 Current_Pending_Sector 0x0022 097 097 000 Old_age Always - 233
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 8019 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 8019 occurred at disk power-on lifetime: 18529 hours (772 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 05 ba 10 70 0c Error: UNC 5 sectors at LBA = 0x0c7010ba = 208670906
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 05 ba 10 70 40 00 39d+12:20:43.030 READ DMA EXT
35 00 0e 4a c5 2c 42 00 39d+12:20:42.981 WRITE DMA EXT
35 00 0f 93 b6 2c 42 00 39d+12:20:42.961 WRITE DMA EXT
35 00 0f 1a b3 2c 42 00 39d+12:20:42.909 WRITE DMA EXT
35 00 0d 5f ab 2c 42 00 39d+12:20:42.854 WRITE DMA EXT
Error 8018 occurred at disk power-on lifetime: 18529 hours (772 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 05 ba 10 70 0c Error: UNC 5 sectors at LBA = 0x0c7010ba = 208670906
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 05 ba 10 70 40 00 39d+12:20:25.930 READ DMA EXT
35 00 0d 5d b4 2c 42 00 39d+12:20:25.831 WRITE DMA EXT
25 00 05 ba 10 70 40 00 39d+12:19:59.457 READ DMA EXT
ef 66 00 00 00 00 00 00 39d+12:19:43.021 SET FEATURES [Disable revert defaults]
ef 02 00 00 00 00 00 00 39d+12:19:43.019 SET FEATURES [Enable write cache]
Error 8017 occurred at disk power-on lifetime: 18529 hours (772 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 01 be 10 70 0c Error: UNC 1 sectors at LBA = 0x0c7010be = 208670910
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 05 ba 10 70 40 00 39d+12:19:59.457 READ DMA EXT
ef 66 00 00 00 00 00 00 39d+12:19:43.021 SET FEATURES [Disable revert defaults]
ef 02 00 00 00 00 00 00 39d+12:19:43.019 SET FEATURES [Enable write cache]
ef aa 00 00 00 00 00 00 39d+12:19:43.018 SET FEATURES [Enable read look-ahead]
ef 03 46 00 00 00 00 00 39d+12:19:43.016 SET FEATURES [Set transfer mode]
Error 8016 occurred at disk power-on lifetime: 18529 hours (772 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 05 ba 10 70 0c Error: UNC 5 sectors at LBA = 0x0c7010ba = 208670906
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 05 ba 10 70 40 00 39d+12:19:21.325 READ DMA EXT
35 00 0d 5c a3 2c 42 00 39d+12:19:21.270 WRITE DMA EXT
35 00 0d 9f a2 2c 42 00 39d+12:19:21.215 WRITE DMA EXT
35 00 0d db a1 2c 42 00 39d+12:19:21.175 WRITE DMA EXT
35 00 58 71 6d fd 41 00 39d+12:19:21.122 WRITE DMA EXT
Error 8015 occurred at disk power-on lifetime: 18529 hours (772 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 05 ba 10 70 0c Error: UNC 5 sectors at LBA = 0x0c7010ba = 208670906
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 05 ba 10 70 40 00 39d+12:19:04.427 READ DMA EXT
35 00 10 20 32 5c 4f 00 39d+12:19:04.377 WRITE DMA EXT
35 00 0b 91 37 23 4f 00 39d+12:19:04.311 WRITE DMA EXT
25 00 08 d1 2c 4c 40 00 39d+12:19:04.249 READ DMA EXT
25 00 05 ba 10 70 40 00 39d+12:18:47.676 READ DMA EXT
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
# zpool status -v
pool: datapool6
state: ONLINE
scan: resilvered 181G in 10h0m with 0 errors on Fri Aug 31 11:34:49 2012
config:
NAME STATE READ WRITE CKSUM
datapool6 ONLINE 0 0 0
raidz2-0 ONLINE 0 0 0
c4t2d0 ONLINE 0 0 0
c4t3d0 ONLINE 0 0 0
c4t4d0 ONLINE 0 0 0
errors: No known data errors
あれれ?なぜ、zfsでは、エラーをはかない?
# zpool scrub datapool6
repairingが始まるが、ひどいことになったので、OFFLINEにした。
# zpool offline datapool6 c4t4d0
# zpool status -v
pool: datapool6
state: DEGRADED
status: One or more devices has been taken offline by the administrator.
Sufficient replicas exist for the pool to continue functioning in a
degraded state.
action: Online the device using 'zpool online' or replace the device with
'zpool replace'.
scan: scrub in progress since Tue Sep 25 23:22:25 2012
2.34G scanned out of 3.21T at 312K/s, (scan is slow, no estimated time)
1.89M repaired, 0.07% done
config:
NAME STATE READ WRITE CKSUM
datapool6 DEGRADED 0 0 0
raidz2-0 DEGRADED 0 0 0
c4t2d0 ONLINE 0 0 0
c4t3d0 ONLINE 0 0 0
c4t4d0 OFFLINE 0 0 0 (repairing)
とりあえず、2本でしばらくがんばってもらおう...orz
FreeBSD9.0R 上で、zfs + sambaの構成で、下記のようなメッセージが表示される。
どうやら、zfsを使ったとき、aclの関係だというのはつかんだけど、全く何が原因か分からない。
困った困った。
smbd[45797]: modules/vfs_posixacl.c:170(smb_ace_to_internal)
smbd[45797]: unknown tag type 64